AGENTS.md@packages/client/src/lib/access-grants agentsA
AGENTS.md@packages/client/src/lib/access-grants is agent-read markdown (agents) from blackbelttechnology/pi-agent-dashboard.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# DOX — packages/client/src/lib/access-grants Files in this directory. One row per source file. | File | Purpose | |------|---------| | `access-grants-api.ts` | Transport for the Settings → Access tab. `fetchAccessSnapshot()` (ONE aggregate `GET /api/access/grants` — the only request the tab issues; render performs zero store writes, task 7.7) + `revokeAccessEntry(entry)` routing per store to ITS OWN write path (task 7.5): path grants → `DELETE /api/access/grants`, worktree trust → `DELETE /api/access/worktree-trust`, KB trust → `DELETE /api/kb/source-trust`, project trust → `DELETE /api/access/project-trust` (the `persistTrustDecision` wrapper — DELETE, never a standing refusal, design D13), trustedNetworks → `DELETE /api/access/trusted-network`, corsOrigins → `DELETE /api/access/cors-origin`, bypassHosts → `DELETE /api/access/bypass-hosts`, pinned dirs → `DELETE /api/access/pinned-directory`. EVERY store is per-entry, so no client snapshot is passed: array-valued config stores are read-modify-written server-side, which is what makes concurrent revokes safe (task 4.5 #5 — previously a whole-array `PUT /api/config` computed from a rendered snapshot, so two revokes could… …
Read the whole file at its exact version.
How to install
mdr add blackbelttechnology/pi-agent-dashboard/packages/client/src/lib/access-grants/AGENTS.md@git:20260921.826475cmdr add blackbelttechnology/pi-agent-dashboard/packages/client/src/lib/access-grants/AGENTS.md@sha256:8ba81447308d49fePin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_ycx22mpalcd6vmvm)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (2831 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 · 299 stars · license MIT · pushed 2026-09-23 · branch develop
API
GET https://markdownregistry.com/api/v1/artifacts/art_ycx22mpalcd6vmvm GET https://markdownregistry.com/api/v1/resolve?ref=blackbelttechnology/pi-agent-dashboard/packages/client/src/lib/access-grants/AGENTS.md GET https://markdownregistry.com/api/v1/blob/8ba81447308d49feb1dc481ee094f351b936b0e444e8e67032095ac6bbb7e35a
Your agent 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.