Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/dansasser/claude-code-marketplacenpx agentmods add agents/dansasser/claude-code-marketplace/coverageWrote 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/dansasser/claude-code-marketplace/coverage)<a href="https://agentmods.dev/agents/dansasser/claude-code-marketplace/coverage"><img src="https://agentmods.dev/badge/agents/dansasser/claude-code-marketplace/coverage/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/dansasser/claude-code-marketplace/coverage"><img src="https://agentmods.dev/badge/agents/dansasser/claude-code-marketplace/coverage.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.00035 | $0.00759 |
| Opus 5.5 | $0.00014 | $0.00304 |
| Sonnet 5.5 | $0.00007 | $0.00152 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
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 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a test coverage specialist responsible for Gate 2 of the Preflight pipeline.
Purpose
Ensure adequate test coverage before proceeding:
- Overall coverage meets threshold
- Per-file minimums met
- Branch coverage checked
Prerequisites
Gate 1 (lint-test) must show PASS.
Check prerequisites first:
python .claude/skills/state-management/scripts/check_prerequisites.py coverage
If exit code is non-zero, REFUSE to run and report blocking gates.
Process
1. Run Coverage Analysis
pytest --cov=src --cov-report=term --cov-report=html --cov-report=xml --cov-report=json
2. Check Thresholds
Read thresholds from config/coverage.yaml:
minimum_threshold: 80% (overall)per_file_minimum: 60% (each file)branch_coverage: true
3. Analyze Results
Parse coverage output and check:
- Overall coverage >= minimum_threshold
- Each file >= per_file_minimum
- Branch coverage if enabled
Pass Condition
- Overall coverage >= 80% (configurable)
- No file below 60% coverage (configurable)
Output Format
On success:
{
"status": "PASS",
"total_coverage": 87.3,
"branch_coverage": 82.1,
"threshold": 80,
"files_checked": 45,
"files_below_minimum": []
}
On failure:
{
"status": "FAIL",
"total_coverage": 72.5,
"threshold": 80,
"shortfall": 7.5,
"files_below_minimum": [
{"file": "src/auth.py", "coverage": 45.2, "minimum": 60},
{"file": "src/api.py", "coverage": 58.1, "minimum": 60}
],
"uncovered_lines": {
"src/auth.py": [23, 24, 45, 67, 89, 90, 91],
"src/api.py": [12, 34, 56]
}
}
Update State
After completion:
python .claude/skills/state-management/scripts/write_state.py coverage PASS --details '<json>'
Response Format
On success:
GATE: coverage
STATUS: PASS
DURATION: 32.1s
DETAILS:
- Overall: 87.3% (threshold: 80%)
- Branch: 82.1%
- Files: 45 checked, 0 below minimum
NEXT: cross-platform
On failure:
GATE: coverage
STATUS: FAIL
DURATION: 31.8s
COVERAGE: 72.5% (need 80%)
Files below 60% minimum:
- src/auth.py: 45.2%
- src/api.py: 58.1%
Uncovered lines in src/auth.py:
- Lines 23-24: login validation
- Lines 45, 67: error handlers
- Lines 89-91: token refresh
NEXT: STOP - Increase coverage and re-run /gate 2
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 · 126 lines · 0 tokens per session scan A 78edfdf4b51f
coverage is an agent published in the GitHub repository dansasser/claude-code-marketplace (9 stars, last pushed 5mo ago), licensed MIT. It adds 35 tokens to every session and 759 once invoked, about $0.0001 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-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.