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-approve/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-approve)<a href="https://agentmods.dev/skills/seanrreid/rad_framework/rad-approve"><img src="https://agentmods.dev/badge/skills/seanrreid/rad_framework/rad-approve/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-approve"><img src="https://agentmods.dev/badge/skills/seanrreid/rad_framework/rad-approve.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.00085 | $0.05620 |
| Opus 5.5 | $0.00034 | $0.02248 |
| Sonnet 5.5 | $0.00017 | $0.01124 |
| Haiku 4.5 | $0.00009 | $0.00562 |
Grade A, and why
rad-approve 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 16d 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 — 502 lines — stays where its author put it; the contents beside it link to each section on GitHub.
rad-approve
Review a pending plan and approve it for execution. Under the Lane B model the
plan doc lives on its rad/[feature] work branch; approval is recorded on that
branch tip. Nothing is committed to the default branch here.
Input
The input — the text the user wrote after the skill name — should be a plan name or path, optionally followed by the proxy-approval flags:
feature-name→ resolves to.agents/plans/feature-name.mdonrad/feature-name.agents/plans/feature-name.md→ used directlyfeature-name --on-behalf-of "Sean R Reid" --evidence "Slack #rad 2026-05-28: 'plan looks good, approve it'"
Proxy approval (--on-behalf-of)
By default this command is architect-only — it gates on the git user's role.
When the architect approves a plan out-of-band (Slack, a PR comment, a verbal
yes in standup) but doesn't run rad-approve (/architect:rad-approve in Claude Code) themselves, a team member may
record that approval with:
--on-behalf-of "<architect name>"— who actually approved. Must resolve to a configured architect in.rad/config.yml(validated, not just typed).--evidence "<text or link>"— required with--on-behalf-of. A quote, Slack permalink, or PR-comment URL showing the architect's approval. This is the audit-trail substitute for the architect running the command themselves.
The recording user's own git identity is captured separately as Recorded-By,
so the record always shows both who approved and who entered it.
If empty, list plans awaiting approval (reading branch tips, since plans live on their work branches):
scripts/rad-status.sh 2>/dev/null | grep pending-review \
|| echo "No pending plans found."
Process
Step 1: Verify authority to approve
First, parse the input (the text the user wrote after the skill name) for the proxy flags. Set PLAN_ARG to the plan
name or path — everything before the first -- flag. Set ON_BEHALF_OF and
EVIDENCE to the values of --on-behalf-of and --evidence if present (empty
otherwise). Every later bash block uses "$PLAN_ARG", "$ON_BEHALF_OF" and
"$EVIDENCE".
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.
- 16d ago Changed · +32 lines 17fc015a4821
- 17d ago Changed · +4 lines 92198ab102fc
- 22d ago First seen · 466 lines · 85 tokens per session scan A e940ba10dd3f
rad-approve is a skill published in the GitHub repository seanrreid/RAD_framework (5 stars, last pushed 4d ago), licensed MIT. It adds 85 tokens to every session and 5,620 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.