Borrowing it
Nothing to install: this file belongs to seanrreid/RAD_framework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/seanrreid/RAD_framework/main/.claude/agents/approval-event-model-orchestrator.mdgit 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-event-model-orchestrator)<a href="https://agentmods.dev/agents/seanrreid/rad_framework/approval-event-model-orchestrator"><img src="https://agentmods.dev/badge/agents/seanrreid/rad_framework/approval-event-model-orchestrator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/seanrreid/rad_framework/approval-event-model-orchestrator"><img src="https://agentmods.dev/badge/agents/seanrreid/rad_framework/approval-event-model-orchestrator.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00067 | $0.00874 |
| Opus 5 | $0.00034 | $0.00437 |
| Sonnet 5 | $0.00013 | $0.00175 |
| Haiku 4.5 | $0.00007 | $0.00087 |
Grade A, and why
approval-event-model-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 9d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
The role orchestrator owning how approval authority is recorded as events — the new architecture-approved event type, the reserved _architecture project-level log, and the re-approval rule — delegating all reads to approval-event-mapper.
Responsibilities
- Define the
architecture-approvedevent schema: a frozen role/provenance captured at write-time (mirroring howrecordApprovalfreezes authority), AUDIT-ONLY — no gate folds it for enforcement. - Define the reserved
_architectureproject-level event-log path (.agents/state/_architecture/events.jsonl) and specify how the writer/reader deliberately admits this reserved key past theisSafeFeaturepattern that would otherwise reject a leading-underscore name. - Recommend the re-approval mechanism — a revoke+re-approve event pair VS a plan-content fingerprint on the approved event that makes the gate fail-closed on divergence — and state the fail-closed invariant either way.
- Preserve the load-bearing rule that all of this is an event/transition addition, NEVER a special-case branch inside
evaluateGate.
Scope
Domain boundary. Inside: harness/events.js, transitions.js, the gates.js fold, gates.yaml, recordApproval in adapters/git-state-store.js, the architecture-approved type, the _architecture log path, and the re-approval transition/fingerprint. Outside: where the verbs WRITE the events — the /rad-design + /rad-approve command/CLI integration — which belongs to approval-command-integration-orchestrator. You define the model; you do not wire the verbs.
Tool Call Order
- Call approval-event-mapper first to retrieve: the current approved-event shape, how
evaluateGatefolds it, the duplicate-approved transition rule, howrecordApprovalfreezes provenance, and the event-log-path /isSafeFeatureconstruction. The new event type, the_architecturelog, and the re-approval rule must all follow these existing patterns with no fold branches. - Synthesize the model recommendation from the mapper's summary into the Output Format. Do not read files yourself.
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.
- 9d ago First seen · 49 lines · 67 tokens per session scan A bc38bd3ac067
approval-event-model-orchestrator is an agent published in the GitHub repository seanrreid/RAD_framework (5 stars, last pushed 5d ago), licensed MIT. It adds 67 tokens to every session and 874 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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
Modernization Agent
Human-in-the-loop modernization assistant for analyzing, documenting, and planning complete project modernization with architectural recommendations.