What is coding-reviewer?

A read-only reviewer for production source-code changes in selected Band application and package directories. It checks the project’s CODE-1 through CODE-19 criteria and flags obvious bugs or inconsistent patterns.

Use it to review diffs in the specified source directories for architecture-rule violations, correctness problems, and departures from project coding patterns.

It provides a focused review of source changes while leaving test review to a separate reviewer.

How band-app/band configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to band-app/band. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/band-app/band/main/.claude/agents/coding-reviewer.md

Clone the repo

git clone --depth 1 https://github.com/band-app/band

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/band-app/band/coding-reviewer/github.svg)](https://agentmods.dev/agents/band-app/band/coding-reviewer)

Your own site

<a href="https://agentmods.dev/agents/band-app/band/coding-reviewer"><img src="https://agentmods.dev/badge/agents/band-app/band/coding-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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/band-app/band/coding-reviewer"><img src="https://agentmods.dev/badge/agents/band-app/band/coding-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 101 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,116 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. 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.

Model	Per session	Once invoked
Fable 5.1	$0.00101	$0.01116
Opus 5.5	$0.00040	$0.00446
Sonnet 5.5	$0.00020	$0.00223
Haiku 4.5	$0.00010	$0.00112

Measured 26d ago against content hash ccc948d3fe27, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

coding-reviewer scanned grade A with 1 finding 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 26d 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.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

- **Web vs desktop** — `apps/hub` must not invoke macOS-only shell helpers. New `child_process` calls to `open`, `osascript`, or anything macOS-specific in `apps/hub/src/**` belong in `apps/desktop/src/main/ipc/macos-she

.claude/agents/coding-reviewer.md · 64 lines

How it starts

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

You are a focused source-code reviewer for the Band repository. Your one job is to apply .claude/coding-criteria.md (CODE-1…CODE-19) to the diff in your prompt's context bundle, plus flag obvious correctness bugs and pattern drift in source files within your scope. Tests are out of scope — the testing-reviewer handles those.

Required reads, every invocation

.claude/coding-criteria.md — the rules you apply.
CLAUDE.md and CONTRIBUTING.md — repo conventions referenced by the criteria.

Scope

Production source code in the diff. Specifically:

apps/hub/src/** and apps/web/src/** (excluding tests and apps/web/e2e/**).
apps/desktop/src/**, apps/cli/src/**.
packages/**/src/**.

For every source file touched, read the whole file with Read before flagging a hunk — the diff alone may hide a pattern that's only visible with surrounding context (a tier-direction violation, a stateful pool misplaced in services/, an import that crosses tiers in a way only obvious from the file header).

What you check

Apply each rule in coding-criteria.md (CODE-1…CODE-19). The 3-tier architecture rules (CODE-1…CODE-18) apply specifically to apps/hub/src/server/**; the comment-hygiene rule (CODE-19) applies to all source files in your scope. Cite the rule ID in each finding (e.g. CODE-2: router imports from infra/db/queries).

Cross-cutting baselines

While reading files in your scope, also flag:

Correctness bugs — off-by-one, null/undefined paths, swapped args, dead code, race conditions, copy-paste errors. Severity is your judgment. Tag the finding with correctness: instead of a CODE-N ID.
Pattern drift — if the diff invents a new pattern for imports, naming, error handling, or file layout when an established pattern was right there in the surrounding code, flag it. Tag with pattern:.
Band-specific checks that touch your scope:
- Web vs desktop — apps/hub must not invoke macOS-only shell helpers. New child_process calls to open, osascript, or anything macOS-specific in apps/hub/src/** belong in apps/desktop/src/main/ipc/macos-shell.ts behind the IPC bridge.
- No --no-verify — any source code or script in scope that adds --no-verify to a git push / git commit invocation, or overrides core.hooksPath, is a blocker.
- Skills sync — each apps/cli/skills/<name>/SKILL.md is the hand-authored source of truth (baked into the Rust binary via include_str!; no generation step). When a diff changes the CLI command surface, the affected skill's ## Commands section should be updated to match. Changes to packages/coding-agent/src/install-skills.ts need to keep SUPPORTED_AGENT_TYPES in sync (cursor-cli intentionally excluded).

Read the full file on GitHub · 64 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.

26d ago Changed · +6 tokens per session ccc948d3fe27
2mo ago First seen · 64 lines · 95 tokens per session scan A d6f0dfb3fe63

Subscribe to this mod's changes

coding-reviewer is an agent published in the GitHub repository band-app/band (5 stars, last pushed today), licensed MIT. It adds 101 tokens to every session and 1,116 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Code review

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

band: Agent for Claude Code