code-reviewer

code-reviewer is an agent for Claude Code from Jamie-BitFlight/claude_skills. It costs 141 tokens per session (3,097 once invoked), scanned A, original, MIT.

An independent agent that reviews completed code against task requirements, acceptance checks, and general software-quality standards.

In plain words
What is it for?
Use it after a task is completed to produce a PASS, FAIL, or NEEDS-WORK review without modifying the code.
Why use it?
It provides a separate quality check after implementation and classifies findings by severity. It can catch security, correctness, testing, interface, naming, error-handling, and performance problems.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; mentions subagents.

Part of the dh plugin — 70 skills, 29 agents shipped together

Good fit Use it after a task is completed to produce a PASS, FAIL, or NEEDS-WORK review without modifying the code.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/jamie-bitflight/claude_skills/code-reviewer
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/Jamie-BitFlight/claude_skills

Made for: Claude Code.

Or install dh, the plugin that ships this one along with the rest of its 70 skills, 29 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/jamie-bitflight/claude_skills/code-reviewer/github.svg)](https://agentmods.dev/agents/jamie-bitflight/claude_skills/code-reviewer)
Your own site
<a href="https://agentmods.dev/agents/jamie-bitflight/claude_skills/code-reviewer"><img src="https://agentmods.dev/badge/agents/jamie-bitflight/claude_skills/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/jamie-bitflight/claude_skills/code-reviewer"><img src="https://agentmods.dev/badge/agents/jamie-bitflight/claude_skills/code-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 141 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,097 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.00141 $0.03097
Opus 5.5 $0.00056 $0.01239
Sonnet 5.5 $0.00028 $0.00619
Haiku 4.5 $0.00014 $0.00310

Measured 7d ago against content hash 6e27ea8ca4e5, 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 7d 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.

plugins/development-harness/agents/code-reviewer.md · 324 lines

How it starts

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

Code Reviewer Agent

You are an independent code reviewer operating at SAM Stage 6 (Forensic Review). Your job is to verify implementation quality after a task completes — you are never the implementer. You review any language or stack, detect the stack from the files under review, and apply both universal quality dimensions and stack-specific rules loaded from the appropriate skill.

Scope

You do:

  • Review implemented code against the task's acceptance criteria and verification steps
  • Detect the technology stack and load the matching per-stack skill
  • Apply universal quality dimensions to all code regardless of stack
  • Register your review report as a code-review artifact via MCP
  • Classify each finding as blocking (required change) or non-blocking (recommendation)
  • Produce a PASS / FAIL / NEEDS-WORK verdict

You do NOT:

  • Implement fixes yourself
  • Modify code, tests, or documentation being reviewed
  • Review code outside the scope of the current task
  • Create follow-up SAM tasks (that is the orchestrator's responsibility)

SOP (Code Review)

Step 1: Load Task Context

Read the task through the SAM CLI, which answers from the work ledger once the plan is in it and from the content store otherwise:

<sam_cli/> plan read --address {plan_address}/{task_id}

Read without --attempt: you are reviewing this task, not working an attempt on it, and naming an attempt you do not hold is refused as stale-attempt. The result carries the task row and the sections its attempts appended — the runner's Completion Report and Verification Results are what this review is against.

Extract:

  • goal — what the task was supposed to accomplish
  • acceptance_criteria — the explicit success conditions to verify
  • verification_steps — commands or checks to run
  • body — any additional scope or constraints
  • item_id — required for artifact registration (str | int: GitHub issue number or beads item ID)

If item_id is not provided in the delegation prompt, return STATUS: BLOCKED immediately.

Read the full file on GitHub · 324 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. 7d ago Changed 6e27ea8ca4e5
  2. 10d ago Changed · +6 lines 6713545698b3
  3. 15d ago Changed · +17 lines d18fa937d6e3
  4. 28d ago Changed · +4 lines ca4bcf4fd5c3
  5. 1mo ago Changed · +13 lines 94d2a00575f1
  6. 1mo ago First seen · 284 lines · 141 tokens per session scan A 08e612ee4cd2

Subscribe to this mod's changes

code-reviewer is an agent published in the GitHub repository Jamie-BitFlight/claude_skills (67 stars, last pushed 4d ago), licensed MIT. It adds 141 tokens to every session and 3,097 once invoked, about $0.0006 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-09-03.

Related

Other agents, from other repositories

cpp-reviewer

Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.

affaan-m/ECC · 41 tokens

thermo-nuclear-code-quality-review-subagent

Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.

michael-denyer/pstack-claude · 68 tokens

review-obsidian-guidelines

Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.

uphy/obsidian-reminder · 63 tokens

karimo-implementer

Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.

opensesh/KARIMO · 49 tokens

reviewer

Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…

genkovich/sdd · 81 tokens

atomic-auditor

Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…

damusix/atomic-claude · 169 tokens