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.
npx agentmods add commands/tommymorgan/claude-plugins/coverage-analysisgit clone --depth 1 https://github.com/tommymorgan/claude-pluginsWhat 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 | $0.00015 | $0.00575 |
| Opus 5 | $0.00008 | $0.00287 |
| Sonnet 5 | $0.00003 | $0.00115 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
tommymorgan: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 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Test Coverage of Living Specifications
Analyzes which scenarios in living .feature files have corresponding tests, identifying coverage gaps.
Usage
/tommymorgan:coverage-analysis [project-path]
What This Does
- Loads living specs from features/ directory
- Discovers test files in project (test_*.py, *.test.js, etc.)
- Matches scenarios to tests using fuzzy name matching
- Reports coverage percentage
- Lists untested scenarios
Process
cd $PROJECT_PATH
python3 tools/claude-plugins/tommymorgan/migration/commands/doc_generator.py coverage features/ .
Output
Test Coverage Analysis
Total scenarios: 15
Tested: 10
Coverage: 66.7%
Scenarios without tests:
✗ User resets password (authentication.feature)
✗ Admin manages permissions (user-management.feature)
✗ Export analytics to CSV (analytics.feature)
✗ Bulk import test cases (test-management.feature)
✗ API rate limiting (api.feature)
Scenarios with tests:
✓ User logs in successfully (test_auth.py::test_user_login)
✓ User logs out (test_auth.py::test_user_logout)
✓ JWT token generation (test_auth.py::test_jwt_generation)
...
Matching Algorithm
Fuzzy matching finds tests that likely correspond to scenarios:
- Converts scenario names to test naming conventions
- Searches test file content for scenario names
- Reports matches with test file names
- Flags scenarios with no matches
Example matches:
- "User logs in successfully" → test_user_login_successfully()
- "JWT token generation" → test_jwt_token_generation()
- "API returns 404 for missing resource" → test_api_404_missing_resource()
Benefits
- Identify gaps: See which scenarios lack test coverage
- Track progress: Monitor coverage as features are implemented
- Quality metric: Quantify test completeness
- Guide testing: Prioritize writing tests for untested scenarios
When to Use
- After implementing features (verify new scenarios are tested)
- Before releases (ensure adequate coverage)
- During code review (check test completeness)
- Sprint retrospectives (discuss coverage trends)
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.
- 2d ago First seen · 94 lines · 15 tokens per session scan A 97b36f572747
tommymorgan:coverage-analysis is a command published in the GitHub repository tommymorgan/claude-plugins (4 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 575 once invoked, about $0.0001 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.