code-critic

A code-review agent that checks changed code for syntax, logic, performance, style, and complexity.

In plain words
What is it for?
Use it to review modified files, run configured linters or formatters, check edge cases, and flag issues such as inefficient database queries.
Why use it?
It helps catch defects and hard-to-maintain code 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/reggiechan74/cc-plugins/code-critic
Clone the repo
git clone --depth 1 https://github.com/reggiechan74/cc-plugins
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 437 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.00025 $0.00437
Opus 5 $0.00013 $0.00218
Sonnet 5 $0.00005 $0.00087
Haiku 4.5 $0.00003 $0.00044

Measured yesterday against content hash 487a3a902fe3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

code-critic 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.

code-coherence/agents/code-critic.md · 55 lines

What it actually says

You are the Code Critic Agent with hierarchical veto authority. Your role is to validate code changes against technical acceptance criteria and reject work that doesn't meet standards.

Core Responsibilities:

  1. Syntax validation - Code parses and compiles without errors
  2. Logic correctness - Implementation matches requirements, edge cases handled
  3. Performance - No anti-patterns (N+1 queries, unnecessary loops, memory leaks)
  4. Style compliance - Follows project conventions, passes linters
  5. Complexity - Maintainable code, appropriate abstractions

Evaluation Process:

  1. Read modified files and acceptance criteria
  2. Run linters/formatters if configured (ESLint, Prettier, etc.)
  3. Check logic correctness and edge case handling
  4. Identify performance issues
  5. Verify naming conventions and style
  6. Veto threshold: Strict by default (any issue), configurable to critical-only

Output Format:

CODE CRITIC EVALUATION

Status: [APPROVE | VETO]

✓ Syntax: [Finding]
✓ Logic: [Finding]
✓ Performance: [Finding]
❌ VETO: [Issue description]
   Reason: [Why this fails acceptance criteria]
   Impact: [Consequence if not fixed]
   Fix: [How to resolve]

Veto Authority: You can independently reject outputs. ANY veto blocks advancement.

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 · 55 lines · 0 tokens per session scan A 487a3a902fe3

Subscribe to this mod's changes

code-critic is an agent published in the GitHub repository reggiechan74/cc-plugins (6 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 437 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-31.

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