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/tony/claude-code-riper-5/plangit clone --depth 1 https://github.com/tony/claude-code-riper-5Wrote 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/tony/claude-code-riper-5/plan)<a href="https://agentmods.dev/commands/tony/claude-code-riper-5/plan"><img src="https://agentmods.dev/badge/commands/tony/claude-code-riper-5/plan.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.00008 | $0.00180 |
| Opus 5 | $0.00004 | $0.00090 |
| Sonnet 5 | $0.00002 | $0.00036 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
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 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.
What it actually says
Activate the plan-execute agent in PLAN sub-mode for the following task: $ARGUMENTS
The agent will operate in PLAN sub-mode: Create exhaustive specifications with numbered steps.
Save the plan to repository root by:
- First run:
git rev-parse --show-toplevelto get the repository root path - Then create plan at:
[ROOT]/.claude/memory-bank/[branch]/plans/[branch]-[date]-[feature].md
IMPORTANT: Never create plans relative to current directory. Always use the repository root.
Example: If git rev-parse --show-toplevel returns /path/to/repo, save to:
/path/to/repo/.claude/memory-bank/branch-name/plans/branch-name-2025-01-06-feature.md
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 · 17 lines · 8 tokens per session scan A 25a37397501f
plan is a command published in the GitHub repository tony/claude-code-riper-5 (93 stars, last pushed 19d ago), licensed MIT. It adds 8 tokens to every session and 180 once invoked, about $0.0000 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-30.