Borrowing it
Nothing to install: this file belongs to jcputney/agent-peer-review. 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/jcputney/agent-peer-review/main/CLAUDE.mdgit clone --depth 1 https://github.com/jcputney/agent-peer-reviewWrote 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/instructions/jcputney/agent-peer-review/claude-md)<a href="https://agentmods.dev/instructions/jcputney/agent-peer-review/claude-md"><img src="https://agentmods.dev/badge/instructions/jcputney/agent-peer-review/claude-md.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.1 | $0.00407 | $0.00407 |
| Opus 5 | $0.00204 | $0.00204 |
| Sonnet 5 | $0.00081 | $0.00081 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
agent-peer-review CLAUDE.md 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 6d 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
Project Conventions
This is a Claude Code plugin marketplace for AI-to-AI peer review.
Architecture
- Subagent Pattern: All Codex CLI work runs in a separate subagent context to prevent context pollution
- Advisory Hooks: Hooks remind Claude to run peer review but don't enforce it
- Marketplace Structure: Designed to host multiple peer review plugins
File Organization
.claude-plugin/marketplace.json # Marketplace registry
plugins/
codex-peer-review/
.claude-plugin/plugin.json # Plugin metadata
agents/ # Subagent definitions
commands/ # Slash commands
skills/ # Skill documentation
hooks/ # Lifecycle hooks
Writing Guidelines
Prompts and Skills
- Keep all prompts language-agnostic - examples should work for any programming language
- Use
codex execfor validating designs/plans,codex reviewonly for actual diffs - Always document both the happy path and error handling
Shell Scripts
- Use
cat << 'EOF'(quoted) for heredocs with special characters - Inject variables separately with
echoafter the heredoc - Handle the case where Codex CLI is not installed
Documentation
- Be accurate about what hooks do (remind vs enforce)
- Include all supported command options
- Keep the README structure diagram updated
Command Selection
| Scenario | Command |
|---|---|
| Reviewing code changes | codex review --base X |
| Validating designs/plans | codex exec "..." |
| Answering questions | codex exec "..." |
Testing Changes
- Install the plugin locally:
/plugin add /path/to/codex-peer-review - Test the
/codex-peer-reviewcommand - Verify hooks display correctly at session start
- Check subagent dispatch works
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.
- 6d ago First seen · 55 lines · 407 tokens per session scan A b05175df6835
agent-peer-review CLAUDE.md is an instructions file published in the GitHub repository jcputney/agent-peer-review (33 stars, last pushed 1mo ago), licensed MIT. It adds 407 tokens to every session, about $0.0020 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.