coverage

A test-coverage check for a project’s automated tests. It verifies overall coverage, coverage for each file, and code paths created by conditional branches before the next preflight step.

In plain words
What is it for?
Use it to run coverage reports, compare results with the project’s configured thresholds, and report whether the coverage gate passes or fails.
Why use it?
It catches code that has little or no test protection and prevents the pipeline from continuing when coverage falls below the configured limits. It runs only after the lint and test check passes.

Agent

Install

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.

agentmods
npx agentmods add agents/dansasser/claude-code-marketplace/coverage
Clone the repo
git clone --depth 1 https://github.com/dansasser/claude-code-marketplace
Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 759 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00035 $0.00759
Opus 5 $0.00017 $0.00380
Sonnet 5 $0.00007 $0.00152
Haiku 4.5 $0.00003 $0.00076

Measured 2d ago against content hash 78edfdf4b51f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

plugins/preflight/agents/coverage.md · 126 lines

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

Read the full file on GitHub · 126 lines

Changes

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.

  1. 2d ago First seen · 126 lines · 0 tokens per session scan A 78edfdf4b51f

Subscribe to this mod's changes

coverage is an agent published in the GitHub repository dansasser/claude-code-marketplace (9 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 759 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.