Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/sifxprime/kodelyth-eccnpx agentmods add commands/sifxprime/kodelyth-ecc/doctorWrote 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/sifxprime/kodelyth-ecc/doctor)<a href="https://agentmods.dev/commands/sifxprime/kodelyth-ecc/doctor"><img src="https://agentmods.dev/badge/commands/sifxprime/kodelyth-ecc/doctor/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/sifxprime/kodelyth-ecc/doctor"><img src="https://agentmods.dev/badge/commands/sifxprime/kodelyth-ecc/doctor.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.00025 | $0.00403 |
| Opus 5.5 | $0.00010 | $0.00161 |
| Sonnet 5.5 | $0.00005 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
doctor 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 1mo 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
/doctor
Runs a health check on your ECC install. Detects drift between what was installed and what is currently on disk.
What It Checks
- Install state file exists and is readable
- Installed version vs latest available
- Agent files present and uncorrupted
- Skills directory intact
- Rules loaded correctly
- Memory store accessible (if applicable)
- Hooks registered (Claude Code only)
Usage
/doctor
Run with no arguments for a full health report on all detected installs.
Implementation
Runs the built-in doctor script:
node scripts/doctor.js
Or with a specific target:
node scripts/doctor.js --target claude-home
node scripts/doctor.js --target windsurf-home
node scripts/doctor.js --target windsurf-project
node scripts/doctor.js --target codex-home
node scripts/doctor.js --target cursor-project
For JSON output (useful in CI or scripts):
node scripts/doctor.js --json
Output
The doctor report shows:
| Field | Meaning |
|---|---|
OK |
Component healthy, no issues |
WARNING |
Potential issue, non-blocking |
ERROR |
Missing or corrupted file, needs attention |
A summary line shows total checked, ok, warnings, and errors.
When to Run
- After first install to confirm everything landed
- After upgrading to a new ECC version
- When an agent or skill isn't behaving as expected
- Before filing a bug report
Related
/update— upgrade to the latest ECC versionuse kodelyth-advisor— if you're not sure where to start
Powered by Kodelyth — trust your install, verify your tools.
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.
- 1mo ago First seen · 76 lines · 25 tokens per session scan A 878578a2706d
doctor is a command published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed 12d ago), licensed MIT. It adds 25 tokens to every session and 403 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
fix-issues
Diagnose, reproduce, then fix reproducible open GitHub issues in parallel: one clean worktree/issue; symlink build artifacts to avoid rebuilds.
investigate
Establish the proven causal chain for the target — from the observed symptom to the root cause that actually explains it — and write a report a fixer or planner can act on without repeating your work. You change nothing and fix nothing: the repository must be exactly as you found it when you finish. No one watches the…
maintainer-review-error-handling
Review the PR for error-handling correctness — surfaced errors, no silent swallows, consistent error patterns (Pi-tuned).
review-errors
Find either defect: a real failure crosses the changed code and becomes indistinguishable from success to the caller, operator, or user who must react; or it escapes its owning item and aborts independent work. Not every error needs logging; recovery is correct when the contract permits it and the right owner can…
toh-fix
Evidence-first debugging — find the root cause with proof before touching code.
check-drift
Run verification and drift checks on the AI knowledge-base to identify missing documentation or stale references.