review Claude Code subagentA
review from tony/claude-code-riper-5 is a Claude Code subagent: a helper Claude Code hands a task to, with its own instructions.
mdr add tony/claude-code-riper-5/.claude/agents/review.md@git:20250906.caea866Pins git:20250906.caea866 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Claude Code subagent
- Repository
- tony/claude-code-riper-5
- Path
.claude/agents/review.md- Versions recorded
- 1
- Latest version
- git:20250906.caea866, committed Sep 6, 2025
- Size
- 5,090 bytes
- Repository stars
- 96
- License
- MIT
Validation and quality assurance - ruthlessly verify implementation against plan.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# RIPER: REVIEW MODE You are operating in **[MODE: REVIEW]** - the validation and quality assurance phase. ## Strict Operational Rules 1. **VALIDATE RUTHLESSLY**: Compare implementation against plan with zero tolerance 2. **NO MODIFICATIONS**: You are FORBIDDEN from: - Fixing issues you find (document them instead) - Making "helpful" adjustments - Implementing missing pieces 3. **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): ```bash git log -n 10 -p # Adjust -n for more/less history ``` Check all changes since plan creation: ```bash git log --oneline --since=[plan-date] ``` Review commit patterns and messages: ```bash git log -n 10 --oneline --author=[implementer] ``` …
Read the whole file at its exact version.
How to install
mdr add tony/claude-code-riper-5/.claude/agents/review.md@sha256:93077c2e0674a631The line at the top of this page pins the label git:20250906.caea866, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_xdyx4rfeqmzxurnt)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in tony/claude-code-riper-5/.claude/agents/review.md since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of review.md from somewhere else? Ask it: where did my review.md come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Sep 6, 2025.
Watch this file (sign in, one email per new version)
Installed this file, say at review.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (5090 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
tony/claude-code-riper-5 · 96 stars · license MIT · pushed 2026-08-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xdyx4rfeqmzxurnt GET https://markdownregistry.com/api/v1/resolve?ref=tony/claude-code-riper-5/.claude/agents/review.md GET https://markdownregistry.com/api/v1/blob/93077c2e0674a631f7b917fef4eca8f823938dae1859f8df8f8822ee8d63140d
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: which agent file does what.
More from tony/claude-code-riper-5
Every file in tony/claude-code-riper-5