coverage-report

coverage-report is a command for Claude Code from armanzeroeight/fastagent-plugins. It costs 10 tokens per session (991 once invoked), scanned A, original, MIT.

A command that runs a project's tests with coverage enabled and shows which code was exercised.

In plain words
What is it for?
Use it to create terminal, HTML, or JSON coverage reports for Jest, Vitest, pytest, or Go projects.
Why use it?
It makes untested lines, branches, and functions easier to find instead of relying on guesswork.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: positional $N argument.

Good fit Use it to create terminal, HTML, or JSON coverage reports for Jest, Vitest, pytest, or Go projects.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/armanzeroeight/fastagent-plugins/coverage-report
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.

Clone the repo
git clone --depth 1 https://github.com/armanzeroeight/fastagent-plugins

Made for: Claude Code.

Wrote 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.

agentmods badge for coverage-report

README.md
[![agentmods](https://agentmods.dev/badge/commands/armanzeroeight/fastagent-plugins/coverage-report/github.svg)](https://agentmods.dev/commands/armanzeroeight/fastagent-plugins/coverage-report)
Your own site
<a href="https://agentmods.dev/commands/armanzeroeight/fastagent-plugins/coverage-report"><img src="https://agentmods.dev/badge/commands/armanzeroeight/fastagent-plugins/coverage-report/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.

agentmods 80×15 button for coverage-report

Your own site · 80×15
<a href="https://agentmods.dev/commands/armanzeroeight/fastagent-plugins/coverage-report"><img src="https://agentmods.dev/badge/commands/armanzeroeight/fastagent-plugins/coverage-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 991 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00010 $0.00991
Opus 5.5 $0.00004 $0.00396
Sonnet 5.5 $0.00002 $0.00198
Haiku 4.5 $0.00001 $0.00099

Measured 1mo ago against content hash 24cbc5d8e671, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

coverage-report 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.

plugins/testing-toolkit/commands/coverage-report.md · 142 lines

How it starts

The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Coverage Report

Context

  • Project type: ![ -f "package.json" ] && echo "Node.js" || [ -f "pyproject.toml" ] && echo "Python" || [ -f "go.mod" ] && echo "Go" || echo "Unknown"
  • Test framework: ![ -f "package.json" ] && (grep -q "jest" package.json && echo "Jest" || grep -q "vitest" package.json && echo "Vitest" || echo "Unknown") || [ -f "pyproject.toml" ] && echo "pytest" || echo "Unknown"
  • Coverage files: !find . -name "coverage" -o -name "htmlcov" -o -name "coverage.out" 2>/dev/null | head -5

Your Task

Generate a comprehensive test coverage report and provide analysis with recommendations.

Arguments

  • $1 (optional): Report format - terminal, html, json, or all (default: terminal)

Steps

  1. Generate coverage report based on framework:

    Jest:

    npm test -- --coverage --coverageReporters=text --coverageReporters=html --coverageReporters=json
    

    Vitest:

    vitest run --coverage
    

    pytest:

    pytest --cov=src --cov-report=term-missing --cov-report=html --cov-report=json
    

    Go:

    go test -coverprofile=coverage.out ./...
    go tool cover -func=coverage.out
    
  2. Display terminal report with key metrics:

    • Overall coverage percentage
    • Line coverage
    • Branch coverage
    • Function coverage
    • Statement coverage
  3. Analyze coverage data and identify:

    • Files with 0% coverage
    • Files with <50% coverage
    • Critical files with low coverage
    • Uncovered branches and error paths
  4. Provide recommendations:

    High Priority (address first):

    • List files with 0% coverage
    • Identify critical business logic with low coverage
    • Highlight security-related code without tests

    Medium Priority (address next):

    • List files with <50% coverage
    • Identify API endpoints without tests
    • Highlight database operations without tests

    Low Priority (address if time permits):

    • List files with 50-70% coverage
    • Identify UI components without tests
    • Highlight utility functions with partial coverage

Read the full file on GitHub · 142 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. 1mo ago First seen · 142 lines · 10 tokens per session scan A 24cbc5d8e671

Subscribe to this mod's changes

coverage-report is a command published in the GitHub repository armanzeroeight/fastagent-plugins (29 stars, last pushed 2mo ago), licensed MIT. It adds 10 tokens to every session and 991 once invoked, about $0.0000 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-09-03.