Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/seanrreid/rad_framework/gate-authority-mappergit clone --depth 1 https://github.com/seanrreid/RAD_frameworkWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/seanrreid/rad_framework/gate-authority-mapper)<a href="https://agentmods.dev/agents/seanrreid/rad_framework/gate-authority-mapper"><img src="https://agentmods.dev/badge/agents/seanrreid/rad_framework/gate-authority-mapper.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00059 | $0.00584 |
| Opus 5 | $0.00030 | $0.00292 |
| Sonnet 5 | $0.00012 | $0.00117 |
| Haiku 4.5 | $0.00006 | $0.00058 |
Grade A, and why
gate-authority-mapper scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Read-only context tool that maps the approval event schema, gate event-fold, recordApproval provenance, and approve/deliver gate-check sites for the gate-authority-orchestrator.
Responsibilities
- Locate the
approved-event shape and how evaluateGate folds it over the event history - Trace how recordApproval freezes the
rolefield at write-time and where recordedBy/proxy provenance attaches - Identify the two candidate decision-fire points: approve-time (recordApproval in cli.js) vs deliver-gate-time (state.gate in cli.js)
- Return file:line anchors and event-shape summaries (≤35 lines), never raw file dumps
- Map gate.yaml rule definition to the structural conditions evaluateGate enforces
Scope
Exact read scope: harness/gates.js, harness/gates.yaml, harness/events.js, recordApproval implementation in harness/adapters/git-state-store.js, the gate-check invocation sites in /rad-approve and /rad-deliver commands (harness/cli.js approveCommand and deliverCommand), and scripts/check-plan-approved.sh. Nothing outside this.
Output Format
Return ≤35 lines summarizing: (1) the approved-event shape (file:line anchors); (2) how evaluateGate's fold matches on the frozen role field (file:line); (3) how recordApproval freezes role and where recordedBy/proxy provenance attaches (file:line); (4) the two candidate decision-fire points with their anchor lines. Example anchor format: harness/gates.js:77-99 evaluateGate fold or harness/adapters/git-state-store.js:356-384 recordApproval implementation.
Rules
- Never read files outside the declared scope (harness/gates.js, gates.yaml, events.js, git-state-store.js recordApproval, cli.js approve/deliver commands, check-plan-approved.sh)
- Never spawn sub-agents or call Task — this is a direct read-only mapping tool
- Never return raw file contents — always summarize to file:line anchors + event-shape notes (≤35 lines total)
- Flag the two candidate decision-fire points explicitly: (a) approve-time recordApproval (harness/adapters/git-state-store.js:356) where role is frozen, and (b) deliver-gate-time state.gate call (harness/cli.js:362) where the frozen role is validated
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 30 lines · 59 tokens per session scan A b7c1b8f1a7c4
gate-authority-mapper is an agent published in the GitHub repository seanrreid/RAD_framework (5 stars, last pushed yesterday), licensed MIT. It adds 59 tokens to every session and 584 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.