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/ThisIsSadeghi/KMPilotWrote 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/thisissadeghi/kmpilot/coverage)<a href="https://agentmods.dev/commands/thisissadeghi/kmpilot/coverage"><img src="https://agentmods.dev/badge/commands/thisissadeghi/kmpilot/coverage/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/thisissadeghi/kmpilot/coverage"><img src="https://agentmods.dev/badge/commands/thisissadeghi/kmpilot/coverage.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.00008 | $0.00180 |
| Opus 5.5 | $0.00003 | $0.00072 |
| Sonnet 5.5 | $0.00002 | $0.00036 |
| Haiku 4.5 | $0.00001 | $0.00018 |
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 2mo 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
Generate coverage reports and open them for all feature modules.
Execute these steps:
- Detect features: List all feature modules by checking
feature/*/build.gradle.kts - Run:
./gradlew koverHtmlReport - 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)"
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.
- 2mo ago First seen · 22 lines · 8 tokens per session scan A 9ee831186149
coverage is a command published in the GitHub repository ThisIsSadeghi/KMPilot (55 stars, last pushed 2mo ago), licensed MIT. It adds 8 tokens to every session and 180 once invoked, about $0.0000 per session on Opus 5.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
feature-build
Build a complete mobile feature from description to running code with E2E tests. Orchestrates 6 phases - planning, implementation, testing, build-fix, quality gate, and verification. Auto-detects platform.
feature-build-fix
Compile the feature, run all tests, and iteratively fix compilation errors and test failures until everything passes. Max 5 iterations.
feature-test
Create all tests for an implemented feature - unit tests (ViewModel, UseCase, Repository), Compose UI tests, and E2E user flow tests.
feature-verify
Run final verification - pass@k test metrics, coverage report, and sign-off. Confirms feature is production-ready.
ijfw-audit
Run the IJFW audit gate for the current workflow phase. Usage: /ijfw-audit [phase name].
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.