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/sangrokjung/claude-forge/test-coveragegit clone --depth 1 https://github.com/sangrokjung/claude-forgeWrote 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/sangrokjung/claude-forge/test-coverage)<a href="https://agentmods.dev/commands/sangrokjung/claude-forge/test-coverage"><img src="https://agentmods.dev/badge/commands/sangrokjung/claude-forge/test-coverage.svg" alt="Measured on agentmods" 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.00014 | $0.00183 |
| Opus 5 | $0.00007 | $0.00092 |
| Sonnet 5 | $0.00003 | $0.00037 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
test-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 6d 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.
Copies of this mod
4 near-identical copies found in the catalogue:
- test-coverage — 95% identical, 5 lines differ
- test-coverage — 95% identical, 5 lines differ
- test-coverage — 86% identical, 4 lines differ
- test-coverage — 80% identical, 13 lines differ
What it actually says
Test Coverage
Analyze test coverage and generate missing tests:
-
Run tests with coverage: npm test --coverage or pnpm test --coverage
-
Analyze coverage report (coverage/coverage-summary.json)
-
Identify files below 80% coverage threshold
-
For each under-covered file:
- Analyze untested code paths
- Generate unit tests for functions
- Generate integration tests for APIs
- Generate E2E tests for critical flows
-
Verify new tests pass
-
Show before/after coverage metrics
-
Ensure project reaches 80%+ overall coverage
Focus on:
- Happy path scenarios
- Error handling
- Edge cases (null, undefined, empty)
- Boundary conditions
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.
- 6d ago First seen · 33 lines · 14 tokens per session scan A c714ef5dab95
test-coverage is a command published in the GitHub repository sangrokjung/claude-forge (825 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 183 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-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…
generate-widget
Génération Widget Flutter avec Tests.
api-endpoint
Création Endpoint API Platform.
test-suite
Run comprehensive test suite with coverage analysis.
generate-tests
This command was migrated to a skill in Claude Code 2.1.3. See: examples/skills/generate-tests/SKILL.md.
create-python-tests
Command "create-python-tests" from codeready-toolchain/tarsy, covering writing tests for python llm service, running tests, from project root, from llm-service/ directory and critical rules.