RAD_framework: Command for Claude Code

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

rad-design is a command for Claude Code from seanrreid/RAD_framework. It costs 75 tokens per session (3,590 once invoked), scanned A, original, MIT.

An architect-only command that turns research findings into a project's agent structure. Agents are specialized helpers, and the structure defines what each one may do.

In plain words
What is it for?
Use it after research to design the agent hierarchy and create the project's agent configuration and scope map.
Why use it?
It gives the project clear boundaries for delegated work and requires approval before generating agent files. Approved designs can be regenerated safely if needed.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: reads .claude/ paths; mentions subagents; reads ~/.codex paths.

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 architecture-approve [slug].

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

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/seanrreid/rad_framework/rad-design"><img src="https://agentmods.dev/badge/commands/seanrreid/rad_framework/rad-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 75 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,590 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.00075 $0.03590
Opus 5.5 $0.00030 $0.01436
Sonnet 5.5 $0.00015 $0.00718
Haiku 4.5 $0.00007 $0.00359

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

Security

Grade A, and why

rad-design 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 3d 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-design.md · 363 lines

How it starts

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

/rad-design

Consume a RAD research artifact and generate the agent architecture for the project. This is the A in Research/Architect/Deliver.

One invocation, inline approval. The command designs the agent hierarchy, shows it to you, and asks to approve / edit / cancel. On approval it flips the artifact to approved and proceeds straight to generation in the same run — the review gate is preserved (you always see the boundaries before any agent file is written), but the old "edit Status, then re-type the command" ceremony is gone.

Two entry paths share the same generation logic:

  • Design & Approve — no approved architecture yet: design → inline approve → generate
  • Generate — an already-approved artifact exists: re-running just (re)generates, idempotently. Manual Status: approved edits still work via this path.

Input

$ARGUMENTS is the project slug. Examples: habit-tracker-api, e-commerce-platform

If $ARGUMENTS is empty, list all files in .agents/research/ and ask which project to design.


Mode Detection

Check for .agents/architecture/[slug].md:

  • File exists, Status: approved → skip to Generate (idempotent re-run)
  • Otherwise (file missing, or Status: draft) → run Design & Approve

Design & Approve flows directly into Generate once you approve — it is one continuous run, not two commands.


Design & Approve

Step 1: Read the research artifact

Read .agents/research/[slug].md directly. This is a small structured file — no sub-agent needed.

If the file does not exist, stop:

No research artifact found for '[slug]'.
Run /rad-research first to produce one.

If the research artifact has a ## Mockup section, read the listed mockup file too — it shows the user-visible surface the agent boundaries must serve. A missing section means no mockup; that is fine and never blocks design.

Read the full file on GitHub · 363 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. 3d ago Changed · +19 lines 851736676d11
  2. 21d ago Changed · +15 lines · +5 tokens per session 460480965769
  3. 22d ago Changed · +26 lines 847362c94a87
  4. 27d ago Changed · +6 lines · +3 tokens per session 97064fcdcd60
  5. 1mo ago Changed · +5 lines 45f00f7aacdc
  6. 2mo ago First seen · 292 lines · 67 tokens per session scan A 435586e1022f

Subscribe to this mod's changes

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