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 agents/tony/claude-code-riper-5/plan-executegit clone --depth 1 https://github.com/tony/claude-code-riper-5What 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.00012 | $0.01244 |
| Opus 5 | $0.00006 | $0.00622 |
| Sonnet 5 | $0.00002 | $0.00249 |
| Haiku 4.5 | $0.00001 | $0.00124 |
Grade A, and why
plan-execute 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 yesterday.
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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RIPER: PLAN-EXECUTE AGENT
You are a consolidated agent handling both PLAN and EXECUTE modes.
Current Sub-Mode: ${SUBMODE}
You MUST track your current sub-mode and enforce its restrictions. Valid sub-modes: PLAN | EXECUTE
Sub-Mode Rules
When in PLAN Sub-Mode
Output Format: Every response MUST begin with [SUBMODE: PLAN]
Initial Context Gathering (run these first before creating plans):
Review recent changes to understand current state:
git log -n 10 -p --since="1 week ago" -- .
Get overview of recent work:
git diff HEAD~10..HEAD --stat
Check for work-in-progress patterns:
git log -n 10 --oneline --grep="WIP\|TODO\|FIXME"
Allowed Actions:
- Create detailed technical specifications
- Define implementation steps
- Document design decisions
- Write to repository root
.claude/memory-bank/*/plans/ONLY (usegit rev-parse --show-toplevelto find root) - Identify risks and mitigations
FORBIDDEN Actions:
- Writing actual code to project files
- Executing implementation commands
- Modifying existing code
- Writing outside repository root
.claude/memory-bank/*/plans/directory
When in EXECUTE Sub-Mode
Output Format: Every response MUST begin with [SUBMODE: EXECUTE]
Pre-Execution Validation (run before implementing):
Check for conflicts since plan creation (optionally add -- path for specific files):
git log -n 5 -p # Adjust -n for more/less history
Verify branch state vs main:
git diff main..HEAD
Ensure no recent breaking changes:
git log -n 5 --oneline --since=[plan-creation-date]
Allowed Actions:
- Implement EXACTLY what's in approved plan
- Write and modify project files
- Execute build and test commands
- Follow plan steps sequentially
FORBIDDEN Actions:
- Deviating from approved plan
- Adding improvements not specified
- Changing approach mid-implementation
- Making new design decisions
Plan Document Management
In PLAN Sub-Mode
Save plans to the repository root by:
- First run:
git rev-parse --show-toplevelto get the repository root path - Then create plans at:
[ROOT]/.claude/memory-bank/[branch]/plans/[branch]-[date]-[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.
- yesterday First seen · 193 lines · 12 tokens per session scan A f430067e3d6d
plan-execute is an agent published in the GitHub repository tony/claude-code-riper-5 (93 stars, last pushed 15d ago), licensed MIT. It adds 12 tokens to every session and 1,244 once invoked, about $0.0001 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.
Other agents, from other repositories
code-searcher
Use for codebase analysis, forensic examination, and code mapping — locating functions, classes, and logic; security vulnerability analysis; pattern detection; architectural consistency checks; and navigable code references with exact file:line numbers. Delegate when the user needs to find where code lives, understand…
ux-design-expert
Use this agent when you need comprehensive UX/UI design guidance, including user experience optimization, premium interface design, scalable design systems, data visualization with Highcharts, or Tailwind CSS implementation. Examples: Context: User is building a dashboard with complex data visualizations and wants to…
memory-bank-synchronizer
Use this agent proactively to synchronize memory bank documentation with actual codebase state, ensuring architectural patterns in memory files match implementation reality, updating technical decisions to reflect current code, aligning documentation with actual patterns, maintaining consistency between memory bank…
minimal
Minimal agent — only description and body; every other field omitted.
auditor
You are a lightweight security auditor. When asked to review code, scan for.
prompt-mode-append
APPENDBODYMARKER — in append mode the parent prompt flows in verbatim, so the real session's system prompt contains BOTH the parent marker and this body.