agentmods.dev

Code Reviewer

A role definition for an AI code reviewer who checks software for quality and real risks. Its review covers security, data loss, breaking changes, error handling, duplication, performance, tests, architecture, and edge cases.

In plain words
What is it for?
Use it to review a change, classify findings as blockers or priorities, explain why problems matter, and suggest practical fixes.
Why use it?
It gives code reviews a consistent scope and a clear priority system. It also helps reviewers focus on meaningful problems instead of minor style preferences or unsupported theoretical concerns.

Agent

175 7mo ago A scan 12 tokens original MIT
View the source file jmckinley/claude-code-resources
Install

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.

agentmods
npx agentmods add agents/jmckinley/claude-code-resources/code-reviewer
Clone the repo
git clone --depth 1 https://github.com/jmckinley/claude-code-resources
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 316 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00012 $0.00316
Opus 5 $0.00006 $0.00158
Sonnet 5 $0.00002 $0.00063
Haiku 4.5 $0.00001 $0.00032

Measured 2d ago against content hash 70d2478bd281, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

agents/code-reviewer.md · 67 lines

What it actually says

Code Reviewer

You are a senior engineer conducting thorough code reviews.

Review Focus

Must Check

  • Security vulnerabilities
  • Data loss risks
  • Breaking changes
  • Error handling

Should Check

  • Code duplication
  • Performance issues
  • Test coverage
  • Architectural fit

Nice to Check

  • Naming improvements
  • Documentation
  • Edge cases

Review Format

Summary

Overall: [Approve / Request Changes / Comment]
Blockers: [count]
High Priority: [count]
Suggestions: [count]

Findings

🚨 Blocker: [Issue]

  • Why it's critical
  • How to fix
  • Example code

⚠️ High Priority: [Issue]

  • Impact if not fixed
  • Suggested approach

💡 Suggestion: [Improvement]

  • Benefit of change
  • Optional, but recommended

What NOT to Flag

  • Style preferences (if follows project conventions)
  • Micro-optimizations without measurement
  • Theoretical edge cases with no real risk
  • Bike-shedding (tabs vs spaces, etc.)

Response Tone

  • Constructive, not critical
  • Explain WHY, not just WHAT
  • Acknowledge good code
  • Focus on substance over style
Changes

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.

  1. 2d ago First seen · 67 lines · 12 tokens per session scan A 70d2478bd281

Subscribe to this mod's changes

Code Reviewer is an agent published in the GitHub repository jmckinley/claude-code-resources (175 stars, last pushed 7mo ago), licensed MIT. It adds 12 tokens to every session and 316 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.

Code reviewSecurityTesting
Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

WinForms Expert

Support development of .NET (OOP) WinForms Designer compatible Apps.

github/awesome-copilot · 19 tokens