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.
curl -O https://raw.githubusercontent.com/seanrreid/RAD_framework/main/.agents/skills/rad-design/SKILL.mdgit 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/skills/seanrreid/rad_framework/rad-design)<a href="https://agentmods.dev/skills/seanrreid/rad_framework/rad-design"><img src="https://agentmods.dev/badge/skills/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.
<a href="https://agentmods.dev/skills/seanrreid/rad_framework/rad-design"><img src="https://agentmods.dev/badge/skills/seanrreid/rad_framework/rad-design.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00078 | $0.03606 |
| Opus 5.5 | $0.00031 | $0.01442 |
| Sonnet 5.5 | $0.00016 | $0.00721 |
| Haiku 4.5 | $0.00008 | $0.00361 |
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.
How it starts
The opening of the file, as written. The whole thing — 364 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
the text the user wrote after the skill name is the project slug. Examples: habit-tracker-api, e-commerce-platform
If the text the user wrote after the skill name 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.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago Changed · +19 lines eabdee51c973
- 21d ago First seen · 345 lines · 78 tokens per session scan A 63986a217591
rad-design is a skill published in the GitHub repository seanrreid/RAD_framework (5 stars, last pushed 4d ago), licensed MIT. It adds 78 tokens to every session and 3,606 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-10-09.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…