Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/seanrreid/rad_framework/rad-designgit 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/commands/seanrreid/rad_framework/rad-design)<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="Measured on agentmods" 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 | $0.00067 | $0.02555 |
| Opus 5 | $0.00034 | $0.01277 |
| Sonnet 5 | $0.00013 | $0.00511 |
| Haiku 4.5 | $0.00007 | $0.00255 |
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 4d 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 — 292 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-
approvedartifact exists: re-running just (re)generates, idempotently. ManualStatus: approvededits 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.
Step 2: Design the agent hierarchy
From the research artifact, design the full agent hierarchy. Produce:
Agent Hierarchy tree:
Parent Orchestrator
├── [Domain] Orchestrator roles: [architect | developer | designer]
│ ├── [Context Tool] reads: [scope], returns: [contract]
│ └── [Context Tool] reads: [scope], returns: [contract]
├── [Domain] Orchestrator roles: [...]
│ └── ...
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.
- 4d ago First seen · 292 lines · 67 tokens per session scan A 435586e1022f
rad-design is a command published in the GitHub repository seanrreid/RAD_framework (5 stars, last pushed 8d ago), licensed MIT. It adds 67 tokens to every session and 2,555 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.