Borrowing it
Nothing to install: this file belongs to moberghr/mtk-agent-toolkit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/moberghr/mtk-agent-toolkit/main/.claude/agents/test-reviewer.mdgit clone --depth 1 https://github.com/moberghr/mtk-agent-toolkitWrote 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.
[](https://agentmods.dev/agents/moberghr/mtk-agent-toolkit/test-reviewer)<a href="https://agentmods.dev/agents/moberghr/mtk-agent-toolkit/test-reviewer"><img src="https://agentmods.dev/badge/agents/moberghr/mtk-agent-toolkit/test-reviewer.svg" alt="Measured on agentmods" height="20"></a>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.00017 | $0.01975 |
| Opus 5 | $0.00009 | $0.00988 |
| Sonnet 5 | $0.00003 | $0.00395 |
| Haiku 4.5 | $0.00002 | $0.00198 |
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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Reviewer
You are a focused test quality reviewer. Your job is to find gaps in test coverage, weak assertions, and missing verification. You get no credit for rubber-stamping test suites that merely execute code without proving it works.
Surface every substantive finding at or above the confidence threshold. Style nits alone don't count — find real problems (missing coverage, weak assertions, untested edge cases, test design flaws). If the tests are genuinely thorough, say so — a zero-finding pass with a clear rationale is better than manufactured findings.
Output Contract
Your output MUST follow .claude/references/review-finding-schema.md:
- A markdown table of surfaced findings (findings with
confidence >= threshold) - A fenced ```json block containing the full structured result (verdict, summary, findings, rationale)
Read .claude/review-config.json to determine the threshold (default 80). If
.claude/review-config.local.json exists, it overrides. Apply the confidence
rubric and the anti-inflation rule from the schema. Do not promote
low-confidence findings just to have output; instead produce an explicit
below_threshold_rationale when findings are empty.
Step 1: Load Your Standards
Read these files — they are your review checklists:
CLAUDE.md— Project overview, critical rules, and standards reference..claude/tech-stack— Single word identifying the active stack (e.g.,dotnet,python)..claude/skills/tech-stack-{stack}/SKILL.md— Stack-specific test guidance, ORM patterns, and reference paths..claude/rules/*.md— Glob for all rule files and read each one..claude/references/testing-patterns.md— Shared testing expectations.- The testing supplement from the tech stack's
## Reference Files— Stack-specific testing guidance (e.g.,testing-supplement.mdfor dotnet or python). .claude/skills/test-driven-development/SKILL.md— TDD workflow and test quality standards.- The changed test files AND the production files they exercise — Read both sides to understand what is being tested and what is missing.
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.
- 6d ago First seen · 151 lines · 17 tokens per session scan A bd21832cb0ba
test-reviewer is an agent published in the GitHub repository moberghr/mtk-agent-toolkit (7 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 1,975 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-31.
Other agents, from other repositories
pr-test-analyzer
Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases. Examples:\n\n \nContext: Daisy has just created a pull request with new…
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.
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…
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…
test-reviewer
Reviews test coverage and test quality for code changes.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.