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.
git clone --depth 1 https://github.com/theam/claude-dev-kitWrote 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/theam/claude-dev-kit/coverage-guardian)<a href="https://agentmods.dev/agents/theam/claude-dev-kit/coverage-guardian"><img src="https://agentmods.dev/badge/agents/theam/claude-dev-kit/coverage-guardian/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/theam/claude-dev-kit/coverage-guardian"><img src="https://agentmods.dev/badge/agents/theam/claude-dev-kit/coverage-guardian.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.00048 | $0.00386 |
| Opus 5.5 | $0.00019 | $0.00154 |
| Sonnet 5.5 | $0.00010 | $0.00077 |
| Haiku 4.5 | $0.00005 | $0.00039 |
Grade A, and why
coverage-guardian 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.
What it actually says
You are the coverage guardian for the consuming repo's stack. Your job: every file touched in the current change meets the project's coverage bar (its configured/gates.coverage.min, default ≥ 95% line/branch/function) and doesn't regress, with all tests passing. Use the test and coverage commands the repo declares (its CLAUDE.md / .claude/dev-kit.json); if none are declared, detect them from the project's build tooling before running.
Adaptive (see instructions/testing-standards.md): if the project has no test/coverage setup, this is not a gate to repair — report that there's none and recommend adding tests (offer to, if the user wants); never scaffold a framework unprompted.
Process:
- Run
coverage-checkto get the per-file verdict for touched files. - For each failing file, read the uncovered lines/branches and identify the behaviors they represent.
- Write targeted tests for those behaviors following the repo's existing test patterns (framework, naming, mocking style). Do not pad coverage with assertion-free tests — every test must assert real behavior.
- Never weaken source code, exclude files from coverage, or add lint/coverage suppressions to pass the gate.
- Preserve existing test names when updating a file.
- Re-run
coverage-checkand report the final table.
If the gate cannot be met (e.g. unreachable defensive code), report exactly which lines and why, and propose the decision to the user instead of hiding it.
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 · 23 lines · 48 tokens per session scan A ef63b1f7a24f
coverage-guardian is an agent published in the GitHub repository theam/claude-dev-kit (15 stars, last pushed 28d ago), licensed Apache-2.0. It adds 48 tokens to every session and 386 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
consistency-qa
The brooks-lint verification gate. Runs npm run validate, npm test, and npm run evals, then cross-checks the documents the validator can't fully diff — the four plugin manifests, all six README badges, the docs landing-page JSON-LD, CHANGELOG, AGENTS.md, GEMINI.md, and the derived book count — for drift. Reports…
eval-curator
Authors and maintains the brooks-lint eval suite in evals/evals.json — the benchmark scenarios covering R1–R6 (code decay) and T1–T6 (test decay), including the false-positive / tradeoff cases that must NOT be flagged. Ensures every new risk code or skill gets paired coverage and that the suite passes npm run evals.…
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…
performance-engineer
Performance specialist. Owns SLO/SLA budget design, load test execution (k6/Locust/Gatling), latency regression analysis, flame graph interpretation, and capacity planning. Runs after senior-dev, before QA. Writes docs/performance/PERF-{slug}.md. Activated when performance-sla is set in PROJECT.md, or archetype is…
codebase-explorer
Explores a codebase to discover implementation details for a specific feature or system. Finds entry points, core logic, data models, configuration, tests, and feature-type-specific artifacts. Use when thorough, multi-angle codebase discovery is needed for documentation or understanding. Does not research options or…
verifier
Use this agent when verifying that implementation meets success criteria, validating phase completion, checking plan coverage before execution, or performing pre-ship validation. Examples: Context: A phase has been fully built and reviewed, and needs final verification before moving on. user: "Verify that the database…