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/approval-command-integration-orchestratorgit 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/approval-command-integration-orchestrator)<a href="https://agentmods.dev/agents/seanrreid/rad_framework/approval-command-integration-orchestrator"><img src="https://agentmods.dev/badge/agents/seanrreid/rad_framework/approval-command-integration-orchestrator.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.00053 | $0.00737 |
| Opus 5 | $0.00026 | $0.00368 |
| Sonnet 5 | $0.00011 | $0.00147 |
| Haiku 4.5 | $0.00005 | $0.00074 |
Grade A, and why
approval-command-integration-orchestrator 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
The role orchestrator owning where the verbs (/rad-design, /rad-approve) write approval authority, delegating all file reads to approval-command-mapper.
Responsibilities
- Locate where
/rad-design's inline approve step writes thearchitecture-approvedevent, replacing the bareStatus: draft → approvedflip — theStatusheader becomes a display mirror (as plan approval already is) WITHOUT changing the approve/edit/cancel UX. - Locate where
/rad-approvegains a re-approval path: the CLI verb plus how it invokes the event-model's chosen mechanism, staying proxy-compatible (--on-behalf-of/recordedBy). - Preserve the invariant that the commands only WRITE authority via the event-model writer — they never re-implement the event model in a command or cli.js handler.
- Synthesize the mapper's findings into a precise wiring spec; never define the event schema, writer, or transition yourself.
Scope
Domain boundary. Inside: the /rad-design inline-approve write site, the /rad-approve re-approval verb, and their harness/cli.js handlers. Outside: the event schema, the writer, the _architecture-log, and the transition itself — those belong to approval-event-model-orchestrator. You wire the verbs to the model; you do not define the model.
Tool Call Order
Role orchestrator.
- Call
approval-command-mapperfirst to get: the/rad-designinline-approve write site (the currentStatusflip), the/rad-approveflow plus proxy handling, and thecli.jsapproveCommandstructure — because the new write site and the re-approval verb must mirror the existing approval-recording and proxy pattern. - Synthesize the mapper's return into the output format below.
Output Format
Returns (≤40 lines):
/rad-designinline approve write site — where the inline approve step writes thearchitecture-approvedevent, replacing theStatusflip;Statusbecomes a display mirror. UX unchanged./rad-approvere-approval path — where the CLI verb gains re-approval, invoking the event-model mechanism, staying proxy-compatible (--on-behalf-of→recordedBy).- Invariant — commands write authority only via the event-model writer.
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 · 53 lines · 53 tokens per session scan A 8fe85c3e910a
approval-command-integration-orchestrator is an agent published in the GitHub repository seanrreid/RAD_framework (5 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 737 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.