RAD_framework: Command for Claude Code

.claude/commands/team/rad-review.md

rad-review is a command for Claude Code from seanrreid/RAD_framework. It costs 54 tokens per session (2,274 once invoked), scanned A, original, MIT.

A command that checks changes on a rad/ work branch against its plan and the project's conventions. It also checks whether changed files stay within the planned scope and whether tests cover the acceptance criteria.

In plain words
What is it for?
Use it after implementation and before requesting review, either for the whole branch or for specific files.
Why use it?
It catches work that drifted beyond the plan, violates project rules, or lacks required tests before an architect reviews the proposed changes.

Command for Claude Code

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

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 →

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/team/rad-review.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-review

README.md
[![agentmods](https://agentmods.dev/badge/commands/seanrreid/rad_framework/rad-review.svg)](https://agentmods.dev/commands/seanrreid/rad_framework/rad-review)
Your own site
<a href="https://agentmods.dev/commands/seanrreid/rad_framework/rad-review"><img src="https://agentmods.dev/badge/commands/seanrreid/rad_framework/rad-review.svg" alt="Measured on agentmods" height="20"></a>
Per session 54 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,274 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00054 $0.02274
Opus 5 $0.00027 $0.01137
Sonnet 5 $0.00011 $0.00455
Haiku 4.5 $0.00005 $0.00227

Measured 6d ago against content hash 9690ffae928f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

rad-review 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 6d 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/team/rad-review.md · 256 lines

How it starts

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

/rad-review

Self-review the rad/[feature] work branch before requesting architect review. Catches problems early — better to find them now than in the architect's review of the deliver PR.

Input

$ARGUMENTS (optional): specific files to review. If empty, reviews all changes on the current rad/[feature] branch since it diverged from the default branch.

BASE=$(scripts/get-default-branch.sh)
git diff "$BASE"...HEAD --name-only

Process

Step 1: Load context

  • Read CLAUDE.md conventions and constraints
  • Read the plan file for this work branch:
    BASE=$(scripts/get-default-branch.sh)
    FEATURE=$(git branch --show-current | sed 's#^rad/##')
    PLAN=".agents/plans/$FEATURE.md"
    
  • Read the execution log:
    LOG=$(ls .agents/logs/$FEATURE-*.md 2>/dev/null | tail -1)
    

Step 2: Scope check

scripts/check-scope.sh "$PLAN" "rad/$FEATURE" "$BASE"

The script outputs each changed file as in-scope or out-of-scope. Include its full output in the review report. Any out-of-scope files are HIGH priority.

Step 2b: Lint advisories

scripts/lint-plan.sh "$PLAN"

Run the plan linter against the plan under review and include its full output in the review report. These are advisory only — they surface plan-quality warnings for the architect's attention but do not gate the review or block architect review. This is separate from the Step 2 scope check.

Step 3: Plan fidelity check

For each task in the plan, verify the implementation matches the description:

  • Is the change in the right file at roughly the right location?
  • Does it do what the task described — no more, no less?
  • Were non-goals respected?

Step 3b: Acceptance Criteria coverage

Iterate over every item in the plan's ## Acceptance Criteria list. For each AC#N, verify at least one Wave task's Validate: field cites it. Any AC with no citing task is HIGH priority — the plan declared an outcome that no task delivers. List every uncovered AC by number.

Read the full file on GitHub · 256 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. 6d ago First seen · 256 lines · 54 tokens per session scan A 9690ffae928f

Subscribe to this mod's changes

rad-review is a command published in the GitHub repository seanrreid/RAD_framework (5 stars, last pushed 2d ago), licensed MIT. It adds 54 tokens to every session and 2,274 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.