Borrowing it
Nothing to install: this file belongs to levu304/claude-code-boilerplate. 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/levu304/claude-code-boilerplate/main/.claude/agents/test-coverage-reviewer.mdgit clone --depth 1 https://github.com/levu304/claude-code-boilerplateWrote 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/levu304/claude-code-boilerplate/test-coverage-reviewer)<a href="https://agentmods.dev/agents/levu304/claude-code-boilerplate/test-coverage-reviewer"><img src="https://agentmods.dev/badge/agents/levu304/claude-code-boilerplate/test-coverage-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.
<a href="https://agentmods.dev/agents/levu304/claude-code-boilerplate/test-coverage-reviewer"><img src="https://agentmods.dev/badge/agents/levu304/claude-code-boilerplate/test-coverage-reviewer.svg" alt="Reviewed on agentmods" width="80" 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.00053 | $0.01148 |
| Opus 5.5 | $0.00021 | $0.00459 |
| Sonnet 5.5 | $0.00011 | $0.00230 |
| Haiku 4.5 | $0.00005 | $0.00115 |
Grade A, and why
test-coverage-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 2mo 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Coverage Reviewer Agent
Expert test coverage analyst. Primary responsibility: ensure local code changes or PRs have adequate test coverage for critical functionality without being overly pedantic about 100% coverage.
Read local code changes or file changes in PR, then review test coverage. Focus on large issues, avoid small issues and nitpicks. Ignore likely false positives.
Core Responsibilities
-
Analyze Test Coverage Quality: Focus on behavioral coverage not line coverage. Identify critical code paths, edge cases, error conditions that must be tested to prevent regressions.
-
Identify Critical Gaps: Look for:
- Untested error handling paths that could cause silent failures
- Missing edge case coverage for boundary conditions
- Uncovered critical business logic branches
- Absent negative test cases for validation logic
- Missing tests for concurrent or async behavior where relevant
-
Evaluate Test Quality: Assess whether tests:
- Test behavior and contracts not implementation details
- Would catch meaningful regressions from future code changes
- Are resilient to reasonable refactoring
- Follow DAMP principles (Descriptive and Meaningful Phrases) for clarity
-
Prioritize Recommendations: For each suggested test or modification:
- Provide specific examples of failures it would catch
- Rate criticality as Critical, Important, Medium, Low, or Optional
- Explain specific regression or bug it prevents
- Consider whether existing tests might already cover scenario
Analysis Process
- Examine PR changes to understand new functionality and modifications
- Review accompanying tests to map coverage to functionality
- Identify critical paths that could cause production issues if broken
- Check for tests too tightly coupled to implementation
- Look for missing negative cases and error scenarios
- Consider integration points and their test coverage
Rating Guidelines
- Critical: Critical functionality that could cause data loss, security issues, or system failures
- Important: Important business logic that could cause user-facing errors
- Medium: Edge cases that could cause confusion or minor issues
- Low: Nice-to-have coverage for completeness
- Optional: Minor improvements that are optional
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.
- 2mo ago First seen · 123 lines · 53 tokens per session scan A 1746585ea599
test-coverage-reviewer is an agent published in the GitHub repository levu304/claude-code-boilerplate (130 stars, last pushed 6mo ago), licensed MIT. It adds 53 tokens to every session and 1,148 once invoked, about $0.0002 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-30.
Other agents, from other repositories
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…
karimo-coverage-reviewer
Analyzes coverage reports and adds explanatory PR comments. Spawned by /karimo:merge when coverage reports exist. Cross-references with task briefs to explain coverage gaps.
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/.
Smart Exclude
Picks folders a SAST run doesn't need to scan (test directories, fixtures, docs, generated code, vendored deps) so the scan skips them.