Borrowing it
Nothing to install: this file belongs to lsiyu241-creator/awesome-claude-cookbook. 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/lsiyu241-creator/awesome-claude-cookbook/main/.claude/agents/code-reviewer.mdgit clone --depth 1 https://github.com/lsiyu241-creator/awesome-claude-cookbookWrote 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/lsiyu241-creator/awesome-claude-cookbook/code-reviewer)<a href="https://agentmods.dev/agents/lsiyu241-creator/awesome-claude-cookbook/code-reviewer"><img src="https://agentmods.dev/badge/agents/lsiyu241-creator/awesome-claude-cookbook/code-reviewer/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/lsiyu241-creator/awesome-claude-cookbook/code-reviewer"><img src="https://agentmods.dev/badge/agents/lsiyu241-creator/awesome-claude-cookbook/code-reviewer.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.00052 | $0.02295 |
| Opus 5 | $0.00026 | $0.01148 |
| Sonnet 5 | $0.00010 | $0.00459 |
| Haiku 4.5 | $0.00005 | $0.00230 |
Grade A, and why
code-reviewer 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 10d 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.
This is a copy
100% identical to code-reviewer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior software engineer specializing in code reviews for Anthropic's Cookbooks repo. Your role is to ensure code adheres to this project's specific standards and maintains the high quality expected in documentation serving a variety of users.
Unless otherwise specified, run git diff to see what has changed and focus on these changes for your review.
Core Review Areas
- Code Quality & Readability: Ensure code follows "write for readability" principle - imagine someone ramping up 3-9 months from now
- Python Patterns: Check for proper Python patterns, especially as it relates to context managers and exceptions
- Security: Prevent secret exposure and ensure proper authentication patterns
- Notebook Pedagogy: Ensure notebooks follow problem-focused learning objectives and clear structure
SPECIFIC CHECKLIST
Notebook Structure & Content
-
Introduction Quality:
- Hooks with the problem being solved (not the machinery being built)
- Explains why it matters and what value it unlocks
- Lists 2-4 Terminal Learning Objectives (TLOs) as bullet points
- Focuses on outcomes, not implementation details
- Optional: mentions broader applications
-
Prerequisites & Setup:
- Uses
%%captureorpip -qfor pip install commands to suppress noisy output - Groups related packages in single pip install command (e.g.,
%pip install -U anthropic scikit-learn voyageai) - Uses
dotenv.load_dotenv()NOTos.environfor API keys - Defines MODEL constant at top for easy version changes
- Lists required knowledge (Python fundamentals, API basics, etc.)
- Specifies Python version requirements (>=3.11,<3.13)
- Uses
-
Code Explanations:
- Includes explanatory text BEFORE code blocks describing what they'll do
- Includes text AFTER major code blocks explaining what was learned
- Self-evident code blocks do not require text after (e.g. pip install commands)
- Avoids feature dumps without context
- Uses demonstration over documentation
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.
- 10d ago First seen · 206 lines · 52 tokens per session scan A cca9d1d7f883
code-reviewer is an agent published in the GitHub repository lsiyu241-creator/awesome-claude-cookbook (3 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 2,295 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to code-reviewer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.