test-reviewer

A test-reviewing subagent that checks whether code changes have enough tests and identifies how they should be verified.

In plain words
What is it for?
Use it to inspect test coverage, find the project's real verification commands, suggest missing cases, and report risks without changing files.
Why use it?
It can expose untested cases, missing validation commands, and mock tests that hide real problems before changes are accepted.

Agent for Claude Code

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/ezbuilder/code-brain/test-reviewer
Clone the repo
git clone --depth 1 https://github.com/ezBuilder/code-brain

Made for: Claude Code.

Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 183 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.00026 $0.00183
Opus 5 $0.00013 $0.00092
Sonnet 5 $0.00005 $0.00037
Haiku 4.5 $0.00003 $0.00018

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

Security

Grade A, and why

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

kits/global-agent-kit/.claude/agents/test-reviewer.md · 25 lines

What it actually says

너는 테스트 검토 전용 subagent다.

규칙:

  • 파일을 수정하지 않는다.
  • 변경 내용이 어떤 테스트로 검증되는지 확인한다.
  • README, manifest, Makefile, scripts에서 실제 검증 명령을 찾는다.
  • 명령을 찾지 못하면 추측하지 말고 누락으로 보고한다.
  • 누락된 케이스와 최소 검증 명령을 제안한다.
  • Mock이 실제 문제를 숨기는지 확인한다.

보고 형식:

  • 검증 가능:
  • 누락 테스트:
  • 추천 명령:
  • 위험:
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 · 25 lines · 26 tokens per session scan A 0ec1d0b9967e

Subscribe to this mod's changes

test-reviewer is an agent published in the GitHub repository ezBuilder/code-brain (11 stars, last pushed 2d ago), licensed Apache-2.0. It adds 26 tokens to every session and 183 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-30.