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/agents/review.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/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/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/agents/tony/claude-code-riper-5/review"><img src="https://agentmods.dev/badge/agents/tony/claude-code-riper-5/review.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.00013 | $0.01322 |
| Opus 5.5 | $0.00005 | $0.00529 |
| Sonnet 5.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 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.
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.
- 1mo 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 (95 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 1,322 once invoked, about $0.0001 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 agents, from other repositories
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
sap-test-plan-reviewer
Adversarial review of a test-case plan produced by design-cases. READS the actual ABAP source snapshot (plus findings.md, flow.md, units.md, and the TC-.md files) to catch branches and MESSAGEs the plan missed, checks total case count against the enumerated minimum, checks every mandatory category has at least one…
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
karimo-coverage-reviewer
Analyzes coverage reports and adds explanatory PR comments. Spawned by /karimo:merge when coverage reports exist. Cross-references with task briefs to explain coverage gaps.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.
Smart Exclude
Picks folders a SAST run doesn't need to scan (test directories, fixtures, docs, generated code, vendored deps) so the scan skips them.