What is approval-command-mapper?

A read-only helper that locates the parts of a codebase involved in recording and approving architecture decisions. It reports where those actions happen without showing the underlying file contents.

Use it when adding or reviewing approval commands, re-approval handling, proxy details, or checks that confirm a plan was approved.

It gives another agent the exact places to change without making it search through unrelated files or accidentally edit anything.

How seanrreid/RAD_framework configures Claude Code

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/seanrreid/RAD_framework/main/.claude/agents/approval-command-mapper.md

Clone the repo

git clone --depth 1 https://github.com/seanrreid/RAD_framework

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/seanrreid/rad_framework/approval-command-mapper/github.svg)](https://agentmods.dev/agents/seanrreid/rad_framework/approval-command-mapper)

Your own site

<a href="https://agentmods.dev/agents/seanrreid/rad_framework/approval-command-mapper"><img src="https://agentmods.dev/badge/agents/seanrreid/rad_framework/approval-command-mapper/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/seanrreid/rad_framework/approval-command-mapper"><img src="https://agentmods.dev/badge/agents/seanrreid/rad_framework/approval-command-mapper.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 58 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 581 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00058	$0.00581
Opus 5.5	$0.00023	$0.00232
Sonnet 5.5	$0.00012	$0.00116
Haiku 4.5	$0.00006	$0.00058

Measured 20d ago against content hash 26f6ff832d73, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

approval-command-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 20d 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.

.claude/agents/approval-command-mapper.md · 38 lines

What it actually says

Role

A read-only context tool that maps the /rad-design inline-approve write site, the /rad-approve flow + proxy handling, and the cli.js approve handler for approval-command-integration-orchestrator.

Responsibilities

Locate the /rad-design inline approve step in .claude/commands/architect/rad-design.md where the Status: draft → approved flip happens — the write site a re-approval verb must replace or mirror.
Map the /rad-approve flow in .claude/commands/architect/rad-approve.md, including --on-behalf-of / --evidence / recordedBy proxy handling.
Map the harness/cli.js approveCommand (and any design/approve handler) structure where a re-approval subcommand attaches.
Note scripts/check-plan-approved.sh as the gate-read the re-approval must keep fail-closed.

Scope

Read-only access to exactly these paths — never edit, never read outside this set:

.claude/commands/architect/rad-design.md
.claude/commands/architect/rad-approve.md
harness/cli.js
scripts/check-plan-approved.sh

Output Format

Return ≤35 lines, no raw file dumps. Provide:

The exact /rad-design inline-approve step where the Status flip happens today (the write site to replace), with file:line anchor.
How /rad-approve records approval and handles --on-behalf-of / recordedBy (the pattern the re-approval verb mirrors) — field names and a brief example.
The cli.js approveCommand structure where a re-approval subcommand attaches, with file:line anchor.

Rules

Never read files outside the declared scope.
Never spawn sub-agents or call Task.
Never return raw file contents — always summarize to the output format with file:line anchors.
Always distinguish the WRITE site (where the verb records authority) from the event model itself — map where verbs call the writer, not how the writer works.

Changes

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.

20d ago Changed · +1 lines 26f6ff832d73
22d ago Changed · +1 lines a1646bcced89
2mo ago First seen · 36 lines · 58 tokens per session scan A b87fbc769aa0

Subscribe to this mod's changes

approval-command-mapper is an agent published in the GitHub repository seanrreid/RAD_framework (5 stars, last pushed 4d ago), licensed MIT. It adds 58 tokens to every session and 581 once invoked, about $0.0002 per session on Opus 5.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.

Building agents

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.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens

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.

github/awesome-copilot · 61 tokens

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.

github/awesome-copilot · 11 tokens

WinForms Expert

Support development of .NET (OOP) WinForms Designer compatible Apps.

github/awesome-copilot · 19 tokens

RAD_framework: Agent for Claude Code