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.
git clone --depth 1 https://github.com/oxygen-fragment/claude-modularWrote 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/commands/oxygen-fragment/claude-modular/coverage-analysis)<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/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/commands/oxygen-fragment/claude-modular/coverage-analysis"><img src="https://agentmods.dev/badge/commands/oxygen-fragment/claude-modular/coverage-analysis.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.00000 | $0.00605 |
| Opus 5.5 | $0.00000 | $0.00242 |
| Sonnet 5.5 | $0.00000 | $0.00121 |
| Haiku 4.5 | $0.00000 | $0.00060 |
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 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.
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
```
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 · 98 lines · 0 tokens per session scan A d51459eceff5
coverage-analysis is a command published in the GitHub repository oxygen-fragment/claude-modular (285 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.
Other commands, from other repositories
verify
Grade work that already exists and decide whether it can merge. Runs the project's current unit, integration, and E2E suites plus security scanning and type checking, scores every dimension 0-10, and returns a merge verdict with a VERIFIED-vs-CLAIMED evidence manifest. Writes no test files and edits no source. Use…
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
mutate
Run mutation testing to verify test quality. Builds a custom mutation tool or uses an existing framework, runs mutations, and reports the mutation score with surviving mutants.
paul:verify
Guide manual user acceptance testing of recently built features.
atdd
Start the ATDD workflow for a new feature. Optionally provide a feature description as an argument.