coverage-analysis

coverage-analysis is a command for Claude Code from oxygen-fragment/claude-modular. It costs 0 tokens per session (605 once invoked), scanned A, original, MIT.

A command that examines how much of a codebase is covered by tests and finds important gaps. It also assesses whether tests are useful and maintainable.

In plain words
What is it for?
Use it to find uncovered lines and error paths, identify weak tests, assess risk, and plan specific improvements.
Why use it?
A coverage percentage alone can hide untested edge cases, errors, or critical code.

Command for Claude Code

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/oxygen-fragment/claude-modular/coverage-analysis
Clone the repo
git clone --depth 1 https://github.com/oxygen-fragment/claude-modular

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-analysis

README.md
[![agentmods](https://agentmods.dev/badge/commands/oxygen-fragment/claude-modular/coverage-analysis.svg)](https://agentmods.dev/commands/oxygen-fragment/claude-modular/coverage-analysis)
Your own site
<a href="https://agentmods.dev/commands/oxygen-fragment/claude-modular/coverage-analysis"><img src="https://agentmods.dev/badge/commands/oxygen-fragment/claude-modular/coverage-analysis.svg" alt="Measured on agentmods" height="20"></a>
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 605 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.00605
Opus 5 $0.00000 $0.00302
Sonnet 5 $0.00000 $0.00121
Haiku 4.5 $0.00000 $0.00060

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

Security

Grade A, and why

coverage-analysis 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 5d 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.

.claude/commands/testing/coverage-analysis.md · 98 lines

What it actually says

Coverage Analysis Command

2. **Gap Analysis**
   - Identify critical uncovered code sections
   - Analyze missing edge case coverage
   - Find untested error handling paths
   - Detect dead or unreachable code

3. **Quality Assessment**
   - Evaluate test quality vs coverage percentage
   - Identify superficial or ineffective tests
   - Analyze test maintainability
   - Review test performance and execution time

4. **Risk Assessment**
   - Prioritize coverage gaps by business impact
   - Identify high-risk uncovered code
   - Assess coverage trends over time
   - Evaluate coverage stability

5. **Improvement Recommendations**
   - Generate specific test cases for gaps
   - Recommend refactoring for testability
   - Suggest coverage targets by module
   - Provide implementation roadmap

6. **Reporting and Visualization**
   - Create comprehensive coverage reports
   - Generate visual coverage maps
   - Track coverage trends and history
   - Set up coverage monitoring
# Coverage report includes:
# - Overall coverage percentage
# - Module-by-module breakdown
# - Critical uncovered lines
# - Improvement recommendations
```

```bash
# Analyze specific module coverage
/test:coverage-analysis --module=auth-service

# Detailed module analysis:
# - Function-level coverage
# - Branch coverage analysis
# - Edge case identification
# - Specific test recommendations
```

```bash
# Compare coverage trends
/test:coverage-analysis --compare=last-week

# Trend analysis:
# - Coverage changes over time
# - Regression identification
# - Improvement tracking
# - Quality metrics evolution
```
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. 5d ago First seen · 98 lines · 0 tokens per session scan A d51459eceff5

Subscribe to this mod's changes

coverage-analysis is a command published in the GitHub repository oxygen-fragment/claude-modular (283 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 605 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-30.