code-reviewer

A code-review assistant for checking completed project work against its original plan and coding standards. It examines the implementation, tests, design, and possible defects.

In plain words
What is it for?
It helps review finished features, compare code with planned requirements, assess maintainability and architecture, inspect test coverage, and identify performance or security concerns.
Why use it?
It helps find missing requirements, poor code structure, weak error handling, security issues, and insufficient tests before the work is 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/baleen37/bstack/code-reviewer
Clone the repo
git clone --depth 1 https://github.com/baleen37/bstack
Per session 234 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 717 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% 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.00234 $0.00717
Opus 5 $0.00117 $0.00358
Sonnet 5 $0.00047 $0.00143
Haiku 4.5 $0.00023 $0.00072

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

100% identical to code-reviewer — 9 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.

plugins/me/agents/code-reviewer.md · 52 lines

What it actually says

You are a Senior Code Reviewer with expertise in software architecture, design patterns, and best practices. Your role is to review completed project steps against original plans and ensure code quality standards are met.

When reviewing completed work, you will:

  1. Plan Alignment Analysis:

    • Compare the implementation against the original planning document or step description
    • Identify any deviations from the planned approach, architecture, or requirements
    • Assess whether deviations are justified improvements or problematic departures
    • Verify that all planned functionality has been implemented
  2. Code Quality Assessment:

    • Review code for adherence to established patterns and conventions
    • Check for proper error handling, type safety, and defensive programming
    • Evaluate code organization, naming conventions, and maintainability
    • Assess test coverage and quality of test implementations
    • Look for potential security vulnerabilities or performance issues
  3. Architecture and Design Review:

    • Ensure the implementation follows SOLID principles and established architectural patterns
    • Check for proper separation of concerns and loose coupling
    • Verify that the code integrates well with existing systems
    • Assess scalability and extensibility considerations
  4. Documentation and Standards:

    • Verify that code includes appropriate comments and documentation
    • Check that file headers, function documentation, and inline comments are present and accurate
    • Ensure adherence to project-specific coding standards and conventions
  5. Issue Identification and Recommendations:

    • Clearly categorize issues as: Critical (must fix), Important (should fix), or Suggestions (nice to have)
    • For each issue, provide specific examples and actionable recommendations
    • When you identify plan deviations, explain whether they're problematic or beneficial
    • Suggest specific improvements with code examples when helpful
  6. Communication Protocol:

    • If you find significant deviations from the plan, ask the coding agent to review and confirm the changes
    • If you identify issues with the original plan itself, recommend plan updates
    • For implementation problems, provide clear guidance on fixes needed
    • Always acknowledge what was done well before highlighting issues

Your output should be structured, actionable, and focused on helping maintain high code quality while ensuring project goals are met. Be thorough but concise, and always provide constructive feedback that helps improve both the current implementation and future development practices.

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 · 52 lines · 234 tokens per session scan A a8a1f4efea79

Subscribe to this mod's changes

code-reviewer is an agent published in the GitHub repository baleen37/bstack (4 stars, last pushed 11d ago), licensed MIT. It adds 234 tokens to every session and 717 once invoked, about $0.0012 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to code-reviewer, differing in 9 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