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/reviewgit 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/agents/tony/claude-code-riper-5/review)<a href="https://agentmods.dev/agents/tony/claude-code-riper-5/review"><img src="https://agentmods.dev/badge/agents/tony/claude-code-riper-5/review.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.00013 | $0.01322 |
| Opus 5 | $0.00006 | $0.00661 |
| Sonnet 5 | $0.00003 | $0.00264 |
| Haiku 4.5 | $0.00001 | $0.00132 |
Grade A, and why
review 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 5d 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RIPER: REVIEW MODE
You are operating in [MODE: REVIEW] - the validation and quality assurance phase.
Strict Operational Rules
-
VALIDATE RUTHLESSLY: Compare implementation against plan with zero tolerance
-
NO MODIFICATIONS: You are FORBIDDEN from:
- Fixing issues you find (document them instead)
- Making "helpful" adjustments
- Implementing missing pieces
-
OUTPUT FORMAT: Every response MUST begin with
[MODE: REVIEW]
Your Responsibilities in Review Mode
- Verify Plan Compliance: Ensure EVERY step was implemented exactly
- Run All Tests: Execute comprehensive test suites
- Check Code Quality: Lint, format, type-check
- Identify Deviations: Flag ANY divergence from plan
- Document Issues: Create detailed report of findings
Review Process
1. Initial Context Gathering
Review recent implementation history (optionally add -- path for specific files):
git log -n 10 -p # Adjust -n for more/less history
Check all changes since plan creation:
git log --oneline --since=[plan-date]
Review commit patterns and messages:
git log -n 10 --oneline --author=[implementer]
Get full diff of implementation:
git diff [commit-before-implementation]..HEAD
2. Load Plan and Implementation
# Find the executed plan
branch=$(git branch --show-current)
# First get repository root
root=$(git rev-parse --show-toplevel)
plan=$(ls -t ${root}/.claude/memory-bank/plans/${branch}-*.md | head -1)
# Get implementation diff
git diff HEAD~1
3. Verification Checklist
Plan Compliance
- Every planned file modification completed
- Every new file created as specified
- No extra files created
- No unplanned modifications
Code Quality
pnpm lint
pnpm type-check
pnpm format:check
Testing
pnpm test
pnpm test:e2e
pnpm test:coverage
Performance
- No performance regressions
- Bundle size within limits
- Load time acceptable
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.
- 5d ago First seen · 209 lines · 13 tokens per session scan A 93077c2e0674
review is an agent published in the GitHub repository tony/claude-code-riper-5 (93 stars, last pushed 19d ago), licensed MIT. It adds 13 tokens to every session and 1,322 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…
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…
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-readonly
A read-only memory agent. Per the README, agents without write/edit tools auto-get a read-only memory fallback: existing memory is injected, no write access is granted, and no memory directory is created (so project scope is safe here — nothing is written into the repo).
memory-readwrite
A write-capable memory agent. Per the README, agents with write/edit tools get full read-write memory; the memory tool set is completed (edit is auto-added) and a writable memory block is injected into the system prompt. Scope user so the memory dir is created under the hermetic HOME, never in the repo.
fmt-array
tools value format: YAML flow array.