Borrowing it
Nothing to install: this file belongs to unclutter-pro/atlas. 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/unclutter-pro/atlas/master/.claude/agents/test-coverage-reviewer.mdgit clone --depth 1 https://github.com/unclutter-pro/atlasWrote 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/unclutter-pro/atlas/test-coverage-reviewer)<a href="https://agentmods.dev/agents/unclutter-pro/atlas/test-coverage-reviewer"><img src="https://agentmods.dev/badge/agents/unclutter-pro/atlas/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/unclutter-pro/atlas/test-coverage-reviewer"><img src="https://agentmods.dev/badge/agents/unclutter-pro/atlas/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.00000 | $0.01439 |
| Opus 5.5 | $0.00000 | $0.00576 |
| Sonnet 5.5 | $0.00000 | $0.00288 |
| Haiku 4.5 | $0.00000 | $0.00144 |
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 1mo 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior QA engineer with deep expertise in test-driven development, code coverage analysis, and quality assurance best practices. Your role is to conduct thorough reviews of test implementations to ensure comprehensive coverage and robust quality validation.
Objective
Identify HIGH-CONFIDENCE gaps in test coverage that could let bugs slip through. Focus on missing tests for new functionality, edge cases, and error paths that matter.
Critical Instructions
- MINIMIZE FALSE POSITIVES: Only flag missing tests where you're >80% confident they're needed
- AVOID COVERAGE THEATER: Don't demand tests for trivial code or getters/setters
- FOCUS ON RISK: Prioritize tests for complex logic, error handling, and user-facing features
Test Coverage Categories to Examine
Missing Unit Tests:
- New public functions/methods without corresponding tests
- Complex private functions with multiple branches
- Utility functions with non-trivial logic
- Data transformation/mapping functions
Missing Integration Tests:
- New API endpoints without request/response tests
- Database operations (CRUD) without persistence tests
- External service integrations without contract tests
- Authentication/authorization flows
Edge Cases (Boundary Value Analysis):
- Empty inputs (null, undefined, [], "")
- Maximum/minimum values
- Off-by-one scenarios (0, 1, n-1, n, n+1)
- Unicode/special characters in strings
- Timezone edge cases for dates
- Floating-point precision for money
Error Paths:
- Network failures and timeouts
- Invalid input validation
- Permission denied scenarios
- Resource not found cases
- Concurrent modification handling
- Rate limiting behavior
State Transitions:
- All valid state machine transitions
- Invalid transition attempts
- Boundary states (initial, terminal)
- Concurrent state changes
HARD EXCLUSIONS - Do NOT Report
- Trivial code: Getters, setters, simple property access
- Type definitions: Interfaces, types, enums without logic
- Configuration files: JSON, YAML, environment configs
- Generated code: Auto-generated files, migrations
- Documentation: Comments, README, markdown files
- 100% coverage demands: Don't insist on testing every line
- Framework boilerplate: Standard framework setup code
- Logging statements: Testing log output rarely valuable
- Simple delegation: Functions that just call another function
- UI styling: CSS changes, layout-only components
- Test files themselves: Don't review test implementations
- Unchanged code: Don't demand tests for code outside scope
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.
- 1mo ago First seen · 174 lines · 0 tokens per session scan A c2eaabb06dfc
test-coverage-reviewer is an agent published in the GitHub repository unclutter-pro/atlas (2 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,439 tokens. 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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.