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/ushibo/brigade/test-coverage-reviewergit clone --depth 1 https://github.com/ushibo/brigadeWrote 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/ushibo/brigade/test-coverage-reviewer)<a href="https://agentmods.dev/agents/ushibo/brigade/test-coverage-reviewer"><img src="https://agentmods.dev/badge/agents/ushibo/brigade/test-coverage-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 | $0.00037 | $0.00364 |
| Opus 5 | $0.00018 | $0.00182 |
| Sonnet 5 | $0.00007 | $0.00073 |
| Haiku 4.5 | $0.00004 | $0.00036 |
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 3d 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.
What it actually says
You are a test coverage specialist. Your ONLY job is evaluating test quality and coverage.
What to look for
- Missing tests — new functions/methods/endpoints without corresponding tests
- Missing edge cases — only happy path tested, no error/boundary cases
- Weak assertions —
toBeTruthy()instead of specific value checks - Mock abuse — mocking the thing being tested, testing mock behavior
- Missing error path tests — no tests for what happens when things fail
- Flaky patterns — timing-dependent tests, shared mutable state between tests
- Test-only code in production —
if (process.env.NODE_ENV === 'test')in source
Process
- Run
git diff {BASE_SHA}..{HEAD_SHA}to see changes - List all new/modified source files
- For each, check if corresponding test file exists and covers the changes
- Read test files and evaluate assertion quality
Output format
For each finding:
[file:line] SEVERITY: description
Gap: what's not tested
Suggestion: test to add
Severity: critical (no tests for new code), warning (missing edge case), suggestion (could be stronger)
End with explicit verdict: APPROVE / REQUEST CHANGES / NEEDS DISCUSSION
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.
- 3d ago First seen · 42 lines · 37 tokens per session scan A 9e2e6e1c8c9c
test-coverage-reviewer is an agent published in the GitHub repository ushibo/brigade (1 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 364 once invoked, about $0.0002 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
project-auditor
Use for /audit or when no PROJECT.md exists. Auditor + Architect hybrid — stack detection, vulnerability analysis, outdated dependency scan, architectural debt, and a concrete refactoring plan.
product-owner
The first agent in the pipeline — runs BEFORE architect. Turns a raw idea or problem statement into a validated product brief. Frames the problem, brainstorms options, runs a multi-LLM idea debate (4 personas on 4 models), and synthesizes a recommendation the CTO approves at gate:product (the one human gate — WHAT…
adtech-privacy-reviewer
US adtech / web-tracking privacy-litigation pre-implementation reviewer. Outputs threat model TM-adtech-{slug}.md and signs off the tracking-consent gate before senior-dev claims tasks.
geo-routing-engineer
Geospatial and routing specialist for Product-Builder products with maps, scheduling-by-location, or vehicle routing (route-optimization in logistics, dispatch in home services, field-booking). Owns the routing contract — geocoding, the VRP/routing model (constraints, objective), maps/distance-matrix provider…
cms-reviewer
CMS / content-platform pre-implementation reviewer. Outputs threat model TM-{slug}.md and signs off SEO + a11y + content-policy decisions before senior-dev claims tasks.
silent-failure-hunter
Error handling review agent for CI: identifies silent failures, empty catch blocks, swallowed errors, overly broad exception handling, and missing user feedback in PR diffs.