What is testing-reviewer?

A read-only reviewer for test code, including unit, integration, and end-to-end tests. It checks changes against a repository's testing rules and looks for missing tests or obvious test bugs.

Use it when reviewing changes to test files, fixtures, or browser-test page objects in the Band repository.

It helps catch weak, broken, or inconsistent tests before they are merged, including cases where a user-visible change has no integration test.

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/testing-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/testing-reviewer/github.svg)](https://agentmods.dev/agents/band-app/band/testing-reviewer)

Your own site

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

Per session 106 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 964 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.

Model	Per session	Once invoked
Fable 5.1	$0.00106	$0.00964
Opus 5.5	$0.00042	$0.00386
Sonnet 5.5	$0.00021	$0.00193
Haiku 4.5	$0.00011	$0.00096

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

Security

Grade A, and why

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

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.

.claude/agents/testing-reviewer.md · 59 lines

How it starts

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

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

Required reads, every invocation

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

Scope

Anything matching apps/hub/tests/**, apps/web/tests/**, apps/web/e2e/**, or *.test.ts / *.spec.ts anywhere in the diff. Also covers fixtures under **/fixtures/** and page-object files under **/e2e/pages/**.

Also flag missing tests: a user-observable change in the diff with no integration test added is a blocker per TEST-6. For "missing test" findings, cite the source file the missing test should have covered.

For each new or modified test file, read the whole file with Read — the diff alone hides surrounding setup/teardown that determines whether the test is sound. Where a test fixture is referenced, read the fixture too.

What you check

Apply each rule in testing-criteria.md (TEST-1…TEST-35). Cite the rule ID in each finding (e.g. TEST-4: uses page.route on own /trpc routes).

Cross-cutting baselines

While reading files in your scope, also flag:

Correctness bugs in tests — typo'd assertions, off-by-one in seed data, wrong expect.poll interval, swapped then/when, setup that doesn't actually configure the path under test. Tag with correctness: instead of a TEST-N ID. Severity is your judgment.
Pattern drift — if a new test invents a setup/fixture/locator pattern when an established one was right there in the surrounding suite, flag it. Tag with pattern:.
CODE-19 — no documentation references in test-file comments (citations of docs/*.md, CLAUDE.md, .claude/skills/**, .claude/*-criteria.md). The rule lives in coding-criteria.md but applies to test source the same way; you enforce it inside your scope.

Read the full file on GitHub · 59 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 a9f8bc32da09
2mo ago First seen · 59 lines · 100 tokens per session scan A 4c153957d4e0

Subscribe to this mod's changes

testing-reviewer is an agent published in the GitHub repository band-app/band (5 stars, last pushed today), licensed MIT. It adds 106 tokens to every session and 964 once invoked, about $0.0004 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.

Code review Testing

ai-hygiene-auditor

Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.

athola/claude-night-market · 48 tokens

sap-test-plan-reviewer

Adversarial review of a test-case plan produced by design-cases. READS the actual ABAP source snapshot (plus findings.md, flow.md, units.md, and the TC-.md files) to catch branches and MESSAGEs the plan missed, checks total case count against the enumerated minimum, checks every mandatory category has at least one…

marcellourbani/vscode_abap_remote_fs · 161 tokens

edge-case-explorer

Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…

testdouble/han · 135 tokens

band: Agent for Claude Code