coverage

A command that creates and opens code-coverage reports for every feature module. Code coverage shows which parts of the code are exercised by tests.

In plain words
What is it for?
Use it to inspect coverage for feature view models, repositories, data sources, and screens.
Why use it?
It avoids manually finding each feature and opening its report, making it easier to see where tests may be missing.

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/thisissadeghi/kmpilot/coverage
Clone the repo
git clone --depth 1 https://github.com/ThisIsSadeghi/KMPilot

Made for: Claude Code.

Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 180 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.00008 $0.00180
Opus 5 $0.00004 $0.00090
Sonnet 5 $0.00002 $0.00036
Haiku 4.5 $0.00001 $0.00018

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

Security

Grade A, and why

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.

.claude/commands/coverage.md · 22 lines

What it actually says

Generate coverage reports and open them for all feature modules.

Execute these steps:

  1. Detect features: List all feature modules by checking feature/*/build.gradle.kts
  2. Run: ./gradlew koverHtmlReport
  3. Open all feature reports dynamically:
    for f in feature/*/build.gradle.kts; do
      name=$(dirname "$f" | xargs basename)
      open "feature/$name/build/reports/kover/html/index.html" 2>/dev/null
    done
    

Confirm completion with: "✅ Coverage reports generated and opened for all features (ViewModels, Repositories, DataSources, Screens only)"

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. 2d ago First seen · 22 lines · 8 tokens per session scan A 9ee831186149

Subscribe to this mod's changes

coverage is a command published in the GitHub repository ThisIsSadeghi/KMPilot (56 stars, last pushed 24d ago), licensed MIT. It adds 8 tokens to every session and 180 once invoked, about $0.0000 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.