code-reviewer

code-reviewer is an agent for Claude Code from qGolem/orc. It costs 58 tokens per session (2,542 once invoked), scanned A, original, MIT.

A general code reviewer that examines changes for security, bugs, quality problems, and compliance with project instructions.

In plain words
What is it for?
Use it on pull requests or local changes to review diffs, surrounding code, framework patterns, and security risks.
Why use it?
It filters out low-confidence or purely stylistic comments so developers can focus on likely real problems.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; mentions CLAUDE.md; positional $N argument.

Part of the orc plugin — 28 skills, 27 agents shipped together

Good fit Use it on pull requests or local changes to review diffs, surrounding code, framework patterns, and security risks.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/qgolem/orc/code-reviewer
View source ↗ qGolem/orc
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.

Clone the repo
git clone --depth 1 https://github.com/qGolem/orc

Made for: Claude Code.

Or install orc, the plugin that ships this one along with the rest of its 28 skills, 27 agents.

Wrote 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.

agentmods badge for code-reviewer

README.md
[![agentmods](https://agentmods.dev/badge/agents/qgolem/orc/code-reviewer/github.svg)](https://agentmods.dev/agents/qgolem/orc/code-reviewer)
Your own site
<a href="https://agentmods.dev/agents/qgolem/orc/code-reviewer"><img src="https://agentmods.dev/badge/agents/qgolem/orc/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.

agentmods 80×15 button for code-reviewer

Your own site · 80×15
<a href="https://agentmods.dev/agents/qgolem/orc/code-reviewer"><img src="https://agentmods.dev/badge/agents/qgolem/orc/code-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,542 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00058 $0.02542
Opus 5.5 $0.00023 $0.01017
Sonnet 5.5 $0.00012 $0.00508
Haiku 4.5 $0.00006 $0.00254

Measured 1mo ago against content hash a4f8add6ce82, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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 · 277 lines

How it starts

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

You are a senior code reviewer ensuring high standards of code quality and security.

Review Process

When invoked:

  1. Gather context — Run git diff --staged and git diff to see all changes. If no diff, check recent commits with git log --oneline -5.
  2. Understand scope — Identify which files changed, what feature/fix they relate to, and how they connect.
  3. Read surrounding code — Don't review changes in isolation. Read the full file and understand imports, dependencies, and call sites.
  4. Apply review checklist — Work through each category below, from CRITICAL to LOW.
  5. Report findings — Use the output format below. Only report issues you are confident about (>80% sure it is a real problem).

Confidence-Based Filtering

IMPORTANT: Do not flood the review with noise. Apply these filters:

  • Report if you are >80% confident it is a real issue
  • Skip stylistic preferences unless they violate project conventions
  • Skip issues in unchanged code unless they are CRITICAL security issues
  • Consolidate similar issues (e.g., "5 functions missing error handling" not 5 separate findings)
  • Prioritize issues that could cause bugs, security vulnerabilities, or data loss

Review Checklist

Security (CRITICAL)

These MUST be flagged — they can cause real damage:

  • Hardcoded credentials — API keys, passwords, tokens, connection strings in source
  • SQL injection — String concatenation in queries instead of parameterized queries
  • XSS vulnerabilities — Unescaped user input rendered in HTML/JSX
  • Path traversal — User-controlled file paths without sanitization
  • CSRF vulnerabilities — State-changing endpoints without CSRF protection
  • Authentication bypasses — Missing auth checks on protected routes
  • Insecure dependencies — Known vulnerable packages
  • Exposed secrets in logs — Logging sensitive data (tokens, passwords, PII)
// BAD: SQL injection via string concatenation
const query = `SELECT * FROM users WHERE id = ${userId}`;

// GOOD: Parameterized query
const query = `SELECT * FROM users WHERE id = $1`;
const result = await db.query(query, [userId]);

Read the full file on GitHub · 277 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. 1mo ago First seen · 277 lines · 58 tokens per session scan A a4f8add6ce82

Subscribe to this mod's changes

code-reviewer is an agent published in the GitHub repository qGolem/orc (5 stars, last pushed 7mo ago), licensed MIT. It adds 58 tokens to every session and 2,542 once invoked, about $0.0002 per session on Opus 5.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

code-verifier

Verifies repository-backed claims and implementation feasibility in PRDs, Design Docs, or Work Plans. Use before document review, after implementation, or for reverse-engineered artifact verification.

shinpr/claude-code-workflows · 39 tokens

release-manager

Cuts a brooks-lint release: sets the version in package.json, propagates it across the four plugin manifests and every version-bearing text file via npm run bump, writes the CHANGELOG entry, re-validates, then commits, pushes to main, tags, and publishes the GitHub release. Final pipeline stage of the brooks-harness…

hyhmrright/brooks-lint · 85 tokens

skill-author

Authors and edits brooks-lint skill content — the six shipped skills (skills/{name}/SKILL.md + {name}-guide.md) and the shared framework under skills/shared/. Knows the repo's hard conventions: the Iron Law finding form, the SKILL.md Setup→Process→Mode-line shape, guide step continuity, and the mandatory "Do NOT…

hyhmrright/brooks-lint · 98 tokens

consistency-qa

The brooks-lint verification gate. Runs npm run validate, npm test, and npm run evals, then cross-checks the documents the validator can't fully diff — the four plugin manifests, all six README badges, the docs landing-page JSON-LD, CHANGELOG, AGENTS.md, GEMINI.md, and the derived book count — for drift. Reports…

hyhmrright/brooks-lint · 123 tokens

eval-curator

Authors and maintains the brooks-lint eval suite in evals/evals.json — the benchmark scenarios covering R1–R6 (code decay) and T1–T6 (test decay), including the false-positive / tradeoff cases that must NOT be flagged. Ensures every new risk code or skill gets paired coverage and that the suite passes npm run evals.…

hyhmrright/brooks-lint · 97 tokens

trigger-boundary-auditor

Audits the trigger boundaries of the six brooks-lint skills for false-triggering risk and routing collisions. Use before a release, or after editing any SKILL.md description: field. Read-only — reports findings, makes no edits.

hyhmrright/brooks-lint · 56 tokens