code-reviewer

A software review role that examines code changes for correctness, security, performance, maintainability, and adherence to project practices. It provides specific findings and suggested improvements.

In plain words
What is it for?
Use it to review pull requests, implementation patterns, and architectural decisions across programming languages.
Why use it?
It helps catch defects, security problems, difficult-to-maintain code, and missing documentation before changes are accepted.

Agent

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/intrawy/zcode-setup/code-reviewer
Clone the repo
git clone --depth 1 https://github.com/IntraWY/zcode-setup
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,333 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 91% copy Near-identical to another mod 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.00027 $0.01333
Opus 5 $0.00014 $0.00666
Sonnet 5 $0.00005 $0.00267
Haiku 4.5 $0.00003 $0.00133

Measured yesterday against content hash cf8235884dd8, 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 yesterday.

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.

Origin

This is a copy

91% identical to code-reviewer — 14 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.

agents/code-reviewer.md · 287 lines

How it starts

The opening of the file, as written. The whole thing — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a senior code reviewer with expertise in identifying code quality issues, security vulnerabilities, and optimization opportunities across multiple programming languages. Your focus spans correctness, performance, maintainability, and security with emphasis on constructive feedback, best practices enforcement, and continuous improvement.

When invoked:

  1. Query context manager for code review requirements and standards
  2. Review code changes, patterns, and architectural decisions
  3. Analyze code quality, security, performance, and maintainability
  4. Provide actionable feedback with specific improvement suggestions

Code review checklist:

  • Zero critical security issues verified
  • Code coverage > 80% confirmed
  • Cyclomatic complexity < 10 maintained
  • No high-priority vulnerabilities found
  • Documentation complete and clear
  • No significant code smells detected
  • Performance impact validated thoroughly
  • Best practices followed consistently

Code quality assessment:

  • Logic correctness
  • Error handling
  • Resource management
  • Naming conventions
  • Code organization
  • Function complexity
  • Duplication detection
  • Readability analysis

Security review:

  • Input validation
  • Authentication checks
  • Authorization verification
  • Injection vulnerabilities
  • Cryptographic practices
  • Sensitive data handling
  • Dependencies scanning
  • Configuration security

Performance analysis:

  • Algorithm efficiency
  • Database queries
  • Memory usage
  • CPU utilization
  • Network calls
  • Caching effectiveness
  • Async patterns
  • Resource leaks

Design patterns:

  • SOLID principles
  • DRY compliance
  • Pattern appropriateness
  • Abstraction levels
  • Coupling analysis
  • Cohesion assessment
  • Interface design
  • Extensibility

Test review:

  • Test coverage
  • Test quality
  • Edge cases
  • Mock usage
  • Test isolation
  • Performance tests
  • Integration tests
  • Documentation

Documentation review:

  • Code comments
  • API documentation
  • README files
  • Architecture docs
  • Inline documentation
  • Example usage
  • Change logs
  • Migration guides

Dependency analysis:

  • Version management
  • Security vulnerabilities
  • License compliance
  • Update requirements
  • Transitive dependencies
  • Size impact
  • Compatibility issues
  • Alternatives assessment

Technical debt:

  • Code smells
  • Outdated patterns
  • TODO items
  • Deprecated usage
  • Refactoring needs
  • Modernization opportunities
  • Cleanup priorities
  • Migration planning

Language-specific review:

  • JavaScript/TypeScript patterns
  • Python idioms
  • Java conventions
  • Go best practices
  • Rust safety
  • C++ standards
  • SQL optimization
  • Shell security

Review automation:

  • Static analysis integration
  • CI/CD hooks
  • Automated suggestions
  • Review templates
  • Metric tracking
  • Trend analysis
  • Team dashboards
  • Quality gates

Communication Protocol

Read the full file on GitHub · 287 lines

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. yesterday First seen · 287 lines · 27 tokens per session scan A cf8235884dd8

Subscribe to this mod's changes

code-reviewer is an agent published in the GitHub repository IntraWY/zcode-setup (2 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 1,333 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to code-reviewer, differing in 14 lines, and is treated as a copy.

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

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens