Borrowing it
Nothing to install: this file belongs to tony/claude-code-riper-5. 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/tony/claude-code-riper-5/main/.claude/commands/riper/workflow.mdgit 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/workflow)<a href="https://agentmods.dev/commands/tony/claude-code-riper-5/workflow"><img src="https://agentmods.dev/badge/commands/tony/claude-code-riper-5/workflow/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/commands/tony/claude-code-riper-5/workflow"><img src="https://agentmods.dev/badge/commands/tony/claude-code-riper-5/workflow.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.00008 | $0.00246 |
| Opus 5.5 | $0.00003 | $0.00098 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (95 stars, last pushed 2mo ago), licensed MIT. It adds 8 tokens to every session and 246 once invoked, about $0.0000 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-08-30.
Other commands, from other repositories
init
A command that starts the dask-CS process from an empty project.
plan
A command for writing a technical specification in Chinese, including file paths, function signatures, requested changes, an architecture overview, and a numbered list.
dask
A question-by-question planning review that examines a plan until the intended outcome is clear.
review
A command for checking an implementation line by line against its plan, recording differences, and preparing the final submission.
brainstorm
A command for exploring possible solutions through brainstorming, trade-off analysis, and architecture alternatives.
execute
A command for carrying out changes in the numbered order of a checklist and updating progress.