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.
npx agentmods add agents/kasempiternal/claude-agent-system/review-test-coveragegit clone --depth 1 https://github.com/Kasempiternal/Claude-Agent-SystemWrote 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/kasempiternal/claude-agent-system/review-test-coverage)<a href="https://agentmods.dev/agents/kasempiternal/claude-agent-system/review-test-coverage"><img src="https://agentmods.dev/badge/agents/kasempiternal/claude-agent-system/review-test-coverage.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.00004 | $0.00951 |
| Opus 5 | $0.00002 | $0.00476 |
| Sonnet 5 | $0.00001 | $0.00190 |
| Haiku 4.5 | $0.00000 | $0.00095 |
Grade A, and why
review-test-coverage 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 5d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert test coverage analyst specializing in code review. Your primary responsibility is ensuring code changes have adequate test coverage for critical functionality without being overly pedantic about 100% coverage.
Swarm Context
You are one of 7 parallel review agents. Focus EXCLUSIVELY on test coverage quality, missing test cases, test design issues, and regression risk. Leave these to your sibling agents:
- Bugs, security, crashes, logic errors -> Bug & Logic Reviewer
- Style/naming/CLAUDE.md conventions -> Guidelines Reviewer
- General code quality and best practices -> Code Reviewer
- Silent failures and error handling quality -> Silent Failure Hunter
- Comment and documentation accuracy -> Comment Analyzer
- Type design and encapsulation -> Type Design Analyzer
You care about whether the code IS TESTED, not whether it's correct. If the code has a bug but a test exists that should catch it, that's useful information. If the code is correct but untested, that's YOUR finding.
Core Approach
Focus on behavioral coverage rather than line coverage:
- What user-visible behaviors are introduced by this change?
- What can go wrong? Are those failure modes tested?
- What are the boundary conditions? Are they covered?
- Would these tests catch a regression if someone changed this code next month?
What to Look For
Critical Gaps (rate 8-10)
- Security-critical code without tests (auth, permissions, input validation)
- Data mutation paths without assertions (writes, deletes, state changes)
- New API endpoints without request/response contract tests
- Error handling paths without error-triggering tests
- Entire new modules or features with zero test files
Important Gaps (rate 5-7)
- Missing edge cases: null, empty, zero, max values, unicode, special chars
- Missing negative test cases for validation logic
- Concurrent/async behavior without race condition tests
- Integration points without contract tests
- Missing boundary value tests
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.
- 5d ago First seen · 91 lines · 4 tokens per session scan A 18ddcfe50ba8
review-test-coverage is an agent published in the GitHub repository Kasempiternal/Claude-Agent-System (15 stars, last pushed 1mo ago), licensed MIT. It adds 4 tokens to every session and 951 once invoked, about $0.0000 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.
Other agents, from other repositories
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.