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/doncheli/don-cheli-sddWrote 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/doncheli/don-cheli-sdd/doctor)<a href="https://agentmods.dev/commands/doncheli/don-cheli-sdd/doctor"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/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/doncheli/don-cheli-sdd/doctor"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/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.00076 | $0.00800 |
| Opus 5 | $0.00038 | $0.00400 |
| Sonnet 5 | $0.00015 | $0.00160 |
| Haiku 4.5 | $0.00008 | $0.00080 |
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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dc:doctor
Objetivo
Detectar y reparar automáticamente problemas comunes del framework, estado de git, worktrees, y entorno de desarrollo. Es el "médico" del proyecto.
Uso
/dc:doctor # Diagnóstico completo + reparación automática
/dc:doctor --solo-diagnostico # Solo reportar, no reparar
/dc:doctor --git # Solo problemas de git
/dc:doctor --framework # Solo problemas del framework
Checks Realizados
Git Health
| Check | Detecta | Auto-repair |
|---|---|---|
| Detached HEAD | git status sin branch |
git checkout <branch> |
| Stale lock files | .git/index.lock huérfano |
Eliminar si proceso no existe |
| Worktrees huérfanos | Worktrees sin directorio de trabajo | git worktree prune |
| Branches huérfanas | Branches sin remote y sin actividad > 30 días | Listar para limpieza manual |
| Merge conflicts sin resolver | <<< markers en archivos tracked |
Listar archivos afectados |
| Unstaged changes perdidos | Archivos modificados no commiteados | Warning + sugerir stash |
| Default branch detection | main vs master vs develop | Auto-detectar y configurar |
Framework Health
| Check | Detecta | Auto-repair |
|---|---|---|
| Archivos .dc faltantes | estado.md, plan.md, etc. no existen | Regenerar desde plantilla |
| config.yaml corrupto | YAML inválido | Regenerar con valores default |
| Versión desactualizada | VERSION < latest | Notificar actualización disponible |
| Capturas no procesadas | capturas.md con > 10 items pendientes | Warning |
| Sesión huérfana | Lock de sesión sin proceso activo | Limpiar lock |
| Habilidades faltantes | Referencia a habilidad que no existe | Warning + listar |
Environment Health
| Check | Detecta | Auto-repair |
|---|---|---|
| Node/Python no instalado | Runtime requerido no disponible | Warning con instrucciones |
| Docker no corriendo | Docker daemon parado | Warning |
| Puerto ocupado | Puerto 3000/5432/6379 en uso | Listar procesos |
| .env faltante | No existe .env pero sí .env.example | Copiar .env.example → .env |
| Dependencias desactualizadas | package-lock.json más viejo que package.json | npm install |
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.
- 5d ago First seen · 79 lines · 76 tokens per session scan A 351069d9e6f7
doctor is a command published in the GitHub repository doncheli/don-cheli-sdd (57 stars, last pushed 29d ago), licensed Apache-2.0. It adds 76 tokens to every session and 800 once invoked, about $0.0004 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-09-03.
Other commands, from other repositories
forensics
Post-mortem investigation for failed or stuck workflows. Analyzes git history and planning artifacts.
audit-fix
Run audit, prioritize findings, auto-fix via quick tasks, test, and commit.
fix-issue
A command that takes a GitHub Issue—a tracked bug, request, or question—and guides its fix from investigation through testing and submission. TDD means writing a failing test first, then changing the code until the test passes.
hotfix
An emergency software-fix workflow that moves directly from development to verification and Git commit, skipping the usual planning and design stages.
reapply-patches
Reapply local modifications after a PBR update.
release
Generate or update changelog and release notes from project history.