Borrowing it
Nothing to install: this file belongs to dnsabby/MSITM.6341. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dnsabby/MSITM.6341/main/.claude/commands/test-coverage.mdgit clone --depth 1 https://github.com/dnsabby/MSITM.6341Wrote 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/dnsabby/msitm.6341/test-coverage)<a href="https://agentmods.dev/commands/dnsabby/msitm.6341/test-coverage"><img src="https://agentmods.dev/badge/commands/dnsabby/msitm.6341/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.00000 | $0.00281 |
| Opus 5 | $0.00000 | $0.00140 |
| Sonnet 5 | $0.00000 | $0.00056 |
| Haiku 4.5 | $0.00000 | $0.00028 |
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 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.
This is a copy
91% identical to auto-pilot — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
/test-coverage
Canonical command: ../../Master.Prompt/.claude/commands/test-coverage.md
Read AGENTS.md first.
Use ../../Master.Doc/MSITM.6341/claude.md for app-specific context.
Use ../../Master.Doc/_project/dbu-msitm-6341/claude.md for project-shared runtime context.
Treat ../../Master.Prompt/ as the canonical command/workflow catalog.
Run node ../../Master.Prompt/.claude/scripts/maintenance/orchestration-preflight.js --write before governed planning, research, coding, QA, docs, or DevOps execution.
After every completed prompt or IDE command/workflow, run node ../../Master.Prompt/.claude/scripts/maintenance/shared-memory-sync.js --json --promotion-scope orchestration-alignment --project dbu-msitm-6341 --master-prompt-root ../../Master.Prompt --master-doc-root ../../Master.Doc so all IDEs keep shared-memory cache status and promotion backlog aligned.
Resolve shared scripts through ../../Master.Prompt/.claude/scripts/.
Start with /auto-pilot when the prompt is not explicitly scoped to a different entrypoint.
After successful framework-managed pushes, record acceptance with node ../../Master.Prompt/.claude/scripts/maintenance/orchestration-post-acceptance.js --write --event push.
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 · 14 lines · 0 tokens per session scan A 2ef2e0d91a4f
test-coverage is a command published in the GitHub repository dnsabby/MSITM.6341 (6 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 281 tokens. A static security scan graded it A with 0 findings. It is 91% identical to auto-pilot, differing in 4 lines, and is treated as a copy.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
verify
Run repository verification using the verification-loop skill.
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
check-dev
Type-check a Z specification with fuzz.
laravel-playwright
E2E Playwright patterns; use the laravel:e2e-playwright skill exactly as written.