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/workflowgit 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.00008 | $0.00246 |
| Opus 5 | $0.00004 | $0.00123 |
| Sonnet 5 | $0.00002 | $0.00049 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
workflow 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 3d 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
Full RIPER Workflow
I'll guide you through the complete RIPER workflow for: $ARGUMENTS
Workflow Phases
Phase 1: RESEARCH
First, I'll use the research-innovate agent in RESEARCH sub-mode to understand the current state of the codebase and gather all necessary information.
Phase 2: INNOVATE
Next, I'll use the research-innovate agent in INNOVATE sub-mode to brainstorm different approaches and explore possibilities.
Phase 3: PLAN
Then, I'll use the plan-execute agent in PLAN sub-mode to create detailed technical specifications that you can review.
⚠️ APPROVAL GATE: I will pause here for your explicit approval before proceeding.
Phase 4: EXECUTE
Once approved, I'll use the plan-execute agent in EXECUTE sub-mode to implement exactly what was planned.
Phase 5: REVIEW
Finally, I'll use the review agent to validate the implementation against the plan.
Starting Workflow
Let me begin with the RESEARCH phase for: $ARGUMENTS
[The appropriate agent will be invoked based on the current phase]
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.
- 3d ago First seen · 32 lines · 8 tokens per session scan A dc83df25433a
workflow is a command published in the GitHub repository tony/claude-code-riper-5 (93 stars, last pushed 17d ago), licensed MIT. It adds 8 tokens to every session and 246 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.