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-adoptgit 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-adopt)<a href="https://agentmods.dev/commands/seanrreid/rad_framework/rad-adopt"><img src="https://agentmods.dev/badge/commands/seanrreid/rad_framework/rad-adopt.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.00061 | $0.01851 |
| Opus 5 | $0.00030 | $0.00925 |
| Sonnet 5 | $0.00012 | $0.00370 |
| Haiku 4.5 | $0.00006 | $0.00185 |
Grade A, and why
rad-adopt 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/rad-adopt
Convert a pre-existing issue into a RAD plan. Use this for work that existed before the RAD framework was introduced.
Input
$ARGUMENTS can be:
- A GitHub/GitLab issue URL:
https://github.com/org/repo/issues/42 - An issue number:
#42or42 - A free-form description:
"Fix the login timeout not resetting on activity"
If empty, ask for the issue reference or description before proceeding.
Process
Step 1: Determine role and available agents
Read CLAUDE.md to find:
- The current user's role (architect, developer, or designer)
- The Agent Scope Map
- Which agents are available for this role
Only call agents available to your role. Flag out-of-scope dependencies in the plan rather than working around them.
Step 2: Fetch issue context
If $ARGUMENTS is a URL or issue number:
# GitHub
gh issue view [number-or-url] --json title,body,labels,comments,assignees,url
# GitLab
glab issue view [number-or-url] --output json
Extract:
- Title
- Body / description
- Labels
- Comments (summarize if long — keep to ≤10 lines)
- Issue URL (for
Adopted-From:field)
If the CLI is unavailable or the fetch fails, prompt the user to paste the issue content directly and use that as the description.
If $ARGUMENTS is a free-form description:
Use the description as-is. Set Adopted-From: [description] in the plan header.
Step 3: Summarize what the issue asks for
Before researching the codebase, output a brief interpretation:
Issue: [title or first sentence of description]
Interpreting as: [1-2 sentence plain-language summary of what needs to change]
Is this correct? (yes / clarify)
If the user clarifies, update the interpretation and continue.
Step 4: Research the codebase
Use context tools to confirm what's affected. The issue provides direction — research confirms scope and uncovers what the issue may not have known.
Cap at 10 tool calls. If more are needed, the issue is too large — split it into two adopt commands with narrower scope each.
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 · 243 lines · 61 tokens per session scan A bb20cd60db6a
rad-adopt is a command published in the GitHub repository seanrreid/RAD_framework (5 stars, last pushed 8d ago), licensed MIT. It adds 61 tokens to every session and 1,851 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
project-recap
Generate a visual project recap for context switching.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
m-task-planner
Target: $ARGUMENTS (Default: requirement document(s) discovered in the project).
triage
Triage ServiceNow incidents — list open incidents, assess priority, investigate a specific INC, or analyze trends.
session-log
Create or append a session log entry.
my-tasks
Track, prioritize, and execute tasks with goal alignment and due date awareness. Claude doesn't just remind you — it helps get work done.