RAD_framework: Command for Claude Code

.claude/commands/architect/rad-approve.md

rad-approve is a command for Claude Code from seanrreid/RAD_framework. It costs 81 tokens per session (5,603 once invoked), scanned A, original, MIT.

A command that records approval for a proposed work plan on its dedicated Git branch. An architect can approve it directly, or a team member can record an architect’s earlier approval with supporting evidence.

In plain words
What is it for?
Use it to approve a named plan or plan file, or to document an approval given in Slack, a pull-request comment, or another offline conversation.
Why use it?
It provides the approval record needed before the plan can move to delivery, while keeping that record off the project’s default branch. It also preserves who approved the plan and why the approval is trusted.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions Claude Code.

This is seanrreid/RAD_framework's own configuration. It tells Claude Code how to work on RAD_framework itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything RAD_framework configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is node harness/cli.js checkout "$FEATURE" # fetches + ff-pulls to the remote tip.

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/commands/architect/rad-approve.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.

agentmods badge for rad-approve

README.md
[![agentmods](https://agentmods.dev/badge/commands/seanrreid/rad_framework/rad-approve/github.svg)](https://agentmods.dev/commands/seanrreid/rad_framework/rad-approve)
Your own site
<a href="https://agentmods.dev/commands/seanrreid/rad_framework/rad-approve"><img src="https://agentmods.dev/badge/commands/seanrreid/rad_framework/rad-approve/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.

agentmods 80×15 button for rad-approve

Your own site · 80×15
<a href="https://agentmods.dev/commands/seanrreid/rad_framework/rad-approve"><img src="https://agentmods.dev/badge/commands/seanrreid/rad_framework/rad-approve.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 81 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,603 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00081 $0.05603
Opus 5.5 $0.00032 $0.02241
Sonnet 5.5 $0.00016 $0.01121
Haiku 4.5 $0.00008 $0.00560

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

Security

Grade A, and why

rad-approve 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 16d 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/commands/architect/rad-approve.md · 501 lines

How it starts

The opening of the file, as written. The whole thing — 501 lines — stays where its author put it; the contents beside it link to each section on GitHub.

rad-approve

Review a pending plan and approve it for execution. Under the Lane B model the plan doc lives on its rad/[feature] work branch; approval is recorded on that branch tip. Nothing is committed to the default branch here.

Input

The input — $ARGUMENTS — should be a plan name or path, optionally followed by the proxy-approval flags:

  • feature-name → resolves to .agents/plans/feature-name.md on rad/feature-name
  • .agents/plans/feature-name.md → used directly
  • feature-name --on-behalf-of "Sean R Reid" --evidence "Slack #rad 2026-05-28: 'plan looks good, approve it'"

Proxy approval (--on-behalf-of)

By default this command is architect-only — it gates on the git user's role. When the architect approves a plan out-of-band (Slack, a PR comment, a verbal yes in standup) but doesn't run rad-approve (/architect:rad-approve in Claude Code) themselves, a team member may record that approval with:

  • --on-behalf-of "<architect name>" — who actually approved. Must resolve to a configured architect in .rad/config.yml (validated, not just typed).
  • --evidence "<text or link>" — required with --on-behalf-of. A quote, Slack permalink, or PR-comment URL showing the architect's approval. This is the audit-trail substitute for the architect running the command themselves.

The recording user's own git identity is captured separately as Recorded-By, so the record always shows both who approved and who entered it.

If empty, list plans awaiting approval (reading branch tips, since plans live on their work branches):

scripts/rad-status.sh 2>/dev/null | grep pending-review \
  || echo "No pending plans found."

Process

Step 1: Verify authority to approve

First, parse the input ($ARGUMENTS) for the proxy flags. Set PLAN_ARG to the plan name or path — everything before the first -- flag. Set ON_BEHALF_OF and EVIDENCE to the values of --on-behalf-of and --evidence if present (empty otherwise). Every later bash block uses "$PLAN_ARG", "$ON_BEHALF_OF" and "$EVIDENCE".

Read the full file on GitHub · 501 lines

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.

  1. 16d ago Changed · +32 lines ce589d6accc9
  2. 17d ago Changed · +4 lines a4fced4e4cf1
  3. 22d ago Changed · +25 lines · -1 tokens per session ccca131e349b
  4. 23d ago Changed · +39 lines 73f15592a1f7
  5. 27d ago Changed · +2 lines bc0e33e04b26
  6. 1mo ago Changed · +51 lines 0e20e1be3143
  7. 2mo ago First seen · 348 lines · 82 tokens per session scan A 16a132e09980

Subscribe to this mod's changes

rad-approve is a command published in the GitHub repository seanrreid/RAD_framework (5 stars, last pushed 4d ago), licensed MIT. It adds 81 tokens to every session and 5,603 once invoked, about $0.0003 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.