coverage

A quick command that runs test coverage analysis with pytest, checks the results against a minimum percentage, and lists files with too little coverage.

In plain words
What is it for?
Use it to run `/coverage`, see overall and branch coverage, identify uncovered lines, and determine whether the configured threshold is met.
Why use it?
It lets you check test coverage without running the full pipeline or changing its saved state.

Command

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 commands/dansasser/claude-code-marketplace/coverage
Clone the repo
git clone --depth 1 https://github.com/dansasser/claude-code-marketplace
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 246 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.00000 $0.00246
Opus 5 $0.00000 $0.00123
Sonnet 5 $0.00000 $0.00049
Haiku 4.5 $0.00000 $0.00025

Measured 2d ago against content hash cfd66ddcf4fc, 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/commands/coverage.md · 56 lines

What it actually says

Quick coverage check.

Purpose

Run just the test coverage analysis without the full pipeline.

Process

  1. Run pytest with coverage
  2. Check against threshold (default 80%)
  3. Report files below minimum

Usage

/coverage

Output

COVERAGE CHECK

Overall:  87.3%
Branch:   82.1%
Threshold: 80%

All files above minimum (60%)

Status: PASS

Or on failure:

COVERAGE CHECK

Overall:  72.5% (need 80%)
Shortfall: 7.5%

Files below 60% minimum:
  - src/auth.py: 45.2%
    Uncovered: lines 23-24, 45, 67, 89-91
  - src/api.py: 58.1%
    Uncovered: lines 12, 34, 56

Status: FAIL - Coverage below threshold

Note

This is a quick check - it does NOT update pipeline state. For full pipeline with state tracking, use /preflight or /gate 2.

Use the coverage agent for this check.

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 · 56 lines · 0 tokens per session scan A cfd66ddcf4fc

Subscribe to this mod's changes

coverage is a command published in the GitHub repository dansasser/claude-code-marketplace (9 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 246 tokens. 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.