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/health-report)<a href="https://agentmods.dev/commands/thisissadeghi/kmpilot/health-report"><img src="https://agentmods.dev/badge/commands/thisissadeghi/kmpilot/health-report/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/health-report"><img src="https://agentmods.dev/badge/commands/thisissadeghi/kmpilot/health-report.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.00007 | $0.00553 |
| Opus 5 | $0.00003 | $0.00277 |
| Sonnet 5 | $0.00001 | $0.00111 |
| Haiku 4.5 | $0.00001 | $0.00055 |
Grade A, and why
health-report 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 9d 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
Feature Health Dashboard
Display health status for all feature modules.
Usage
/health-report
Process
- Discover Features:
ls -d feature/*/build.gradle.kts - Check Each Feature:
- Spec:
.claude/docs/{feature}/spec.mdexists? - Tests:
*Test.ktfiles in commonTest? - Review:
.claude/docs/{feature}/review.mdexists?
- Spec:
Output
## Feature Health Report
| Feature | Spec | Tests | Review | Actions |
|---------|------|-------|--------|---------|
| home | ✅ | ✅ 7 files | ✅ | - |
| profile | ✅ | ⚠️ 2 files | ❌ | /review-feature profile |
| login | ❌ | ❌ 0 files | ❌ | /audit-spec login |
### Summary
- **Total:** 3 features
- **With Spec:** 2/3
- **With Tests:** 2/3
- **With Review:** 1/3
Health Criteria
| Check | ✅ Pass | ⚠️ Warning | ❌ Fail |
|---|---|---|---|
| Spec | exists | - | missing |
| Tests | 5+ files | 1-4 files | 0 files |
| Review | exists | - | missing |
After Health Check
Find the biggest gap across all features (the row with the most ❌ entries), then emit the matching literal footer as the very last line of output.
If most features are missing a spec:
---
> **Next step —** run `/clear` to free the context window, then `/audit-spec {feature}` to generate the missing spec for one of the flagged features.
If most features are missing tests:
---
> **Next step —** run `/clear` to free the context window, then `/test-feature {feature}` to generate tests for one of the flagged features.
If most features are missing a review:
---
> **Next step —** run `/clear` to free the context window, then `/review-feature {feature}` to validate one of the flagged features.
If all rows pass:
---
> **Next step —** run `/clear` to free the context window, then `/coverage` to see the full coverage report across all features.
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.
- 9d ago First seen · 86 lines · 7 tokens per session scan A 5efeb195e268
health-report is a command published in the GitHub repository ThisIsSadeghi/KMPilot (57 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 553 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.
Other commands, from other repositories
feature-status
Show the current status of a feature build - which phase is active, what has completed, what remains, and any blockers.
set-tracker
Set the issue tracker for the current project.
resume-project
Run resume-project now — Now / Blocked / Next. Not a cheat sheet.
update-counts
Update all hardcoded counts (skills, agents, marketplace repos/skills) across documentation from filesystem.
iniciar
Inicializar Don Cheli en un proyecto nuevo o existente.
go
You are the Project Kickstart agent. Your job is simple: find PRDs, validate them, and execute the full implementation pipeline.