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-plan/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-plan)<a href="https://agentmods.dev/skills/seanrreid/rad_framework/rad-plan"><img src="https://agentmods.dev/badge/skills/seanrreid/rad_framework/rad-plan/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-plan"><img src="https://agentmods.dev/badge/skills/seanrreid/rad_framework/rad-plan.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.00083 | $0.05248 |
| Opus 5.5 | $0.00033 | $0.02099 |
| Sonnet 5.5 | $0.00017 | $0.01050 |
| Haiku 4.5 | $0.00008 | $0.00525 |
Grade A, and why
rad-plan 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 17d 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 — 516 lines — stays where its author put it; the contents beside it link to each section on GitHub.
rad-plan
Research and plan a feature within your agent boundaries. The plan doc lives on
its own rad/[feature] work branch (Lane B): nothing is committed to the default
branch here. The architect approves with rad-approve (/architect:rad-approve in
Claude Code) — there is no plan PR. The
plan and its code reach the default branch later, together, via the single
deliver PR.
Input
The input (the text the user wrote after the skill name) should describe the feature or bug fix. Examples:
- "Add skeleton loading states to the habit list"
- "Fix the date picker not respecting user timezone"
- "Add export to CSV for the weekly summary"
If the text the user wrote after the skill name is empty, ask for a description before proceeding.
--light may prefix the description to request a light-tier plan — a
condensed, single-wave plan for a small, low-risk change:
- "--light Fix the typo in the onboarding guide"
Without --light, every step below runs in standard mode, unchanged.
--override-disposition "<reason>" may accompany the description to proceed
past a research artifact's cited non-actionable disposition (see Step 0). The
override and its reason are recorded in the plan header.
--playbook <kind>/<slug>[@<version>] may accompany the description to start from a
pinned playbook in .agents/playbooks/ (see Step 1b). A bare ref pins the
playbook's current version.
Process
Step 0: Check the research disposition
Derive the feature slug the same way Step 3 does (kebab-case; if the text the user wrote after the skill name
names a research slug, use it). If .agents/research/[feature-slug].md does not
exist, skip this step — no research artifact, no check.
Otherwise run:
scripts/check-disposition.sh .agents/research/[feature-slug].md
# when the text the user wrote after the skill name includes --override-disposition "<reason>":
scripts/check-disposition.sh .agents/research/[feature-slug].md --override "<reason>"
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.
- 17d ago Changed · +3 lines 9497ff61ca23
- 20d ago Changed · +58 lines b09c5884f0d0
- 22d ago First seen · 455 lines · 83 tokens per session scan A 1b68c09f6e23
rad-plan is a skill published in the GitHub repository seanrreid/RAD_framework (5 stars, last pushed 4d ago), licensed MIT. It adds 83 tokens to every session and 5,248 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-08.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.