AGENTS.md@.github/verdaccioA
AGENTS.md@.github/verdaccio from blackbelttechnology/pi-agent-dashboard is an AGENTS.md file: the standing instructions coding agents read in that repo.
mdr add blackbelttechnology/pi-agent-dashboard/.github/verdaccio/AGENTS.md@git:20260720.e108f63Pins git:20260720.e108f63 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- AGENTS.md file
- Repository
- blackbelttechnology/pi-agent-dashboard
- Path
.github/verdaccio/AGENTS.md- Versions recorded
- 1
- Latest version
- git:20260720.e108f63, committed Jul 20, 2026
- Size
- 891 bytes
- Repository stars
- 339
- License
- MIT
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# DOX — .github/verdaccio Files in this directory. One row per file. Non-source area. | File | Purpose | |------|---------| | `config.yml` | Verdaccio config, nightly round-trip (change: add-nightly-verdaccio-build). Ephemeral loopback registry. `_electron-build.yml` starts it per Electron leg when `registry_url` set. `uplinks.npmjs` → https://registry.npmjs.org/. `packages['@blackbelt-technology/*']`: `access/publish/unpublish $all`, **no `proxy`** — local-only shadow. Local `<base>` publish avoids EPUBLISHCONFLICT vs public `<base>`. `^<base>` resolves just-published working-tree source → nightly tests UNRELEASED code. `packages['**']`: `access/publish $all` + `proxy: npmjs` — third-party deps proxy + cache public npm. `listen: 127.0.0.1:4873` (loopback bind, unauthenticated registry never public). Anonymous, no token. `web.enable: false`. See design Decision 2. |
Read the whole file at its exact version.
How to install
mdr add blackbelttechnology/pi-agent-dashboard/.github/verdaccio/AGENTS.md@sha256:74b74dfc5f55bbb6The line at the top of this page pins the label git:20260720.e108f63, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_lxwlymv5q6zmrxdg)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 20, 2026.
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (891 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
blackbelttechnology/pi-agent-dashboard · 339 stars · license MIT · pushed 2026-11-02 · branch develop
API
GET https://markdownregistry.com/api/v1/artifacts/art_lxwlymv5q6zmrxdg GET https://markdownregistry.com/api/v1/resolve?ref=blackbelttechnology/pi-agent-dashboard/.github/verdaccio/AGENTS.md GET https://markdownregistry.com/api/v1/blob/74b74dfc5f55bbb69b84321c515559b6856b5e35ce1150f86ae5cabe42446893
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: how to write a good AGENTS.md · AGENTS.md vs CLAUDE.md · which agent file does what.