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.
npx agentmods add commands/doncheli/don-cheli-sdd/completogit 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/completo)<a href="https://agentmods.dev/commands/doncheli/don-cheli-sdd/completo"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/completo.svg" alt="Measured on agentmods" 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.00013 | $0.00378 |
| Opus 5 | $0.00006 | $0.00189 |
| Sonnet 5 | $0.00003 | $0.00076 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade A, and why
completo 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.
What it actually says
/dc:completo
Objetivo
Iniciar modo completo (Nivel 3 - Complejo) para proyectos que requieren las 7 fases del ciclo de vida.
Uso
/dc:completo <descripción del proyecto>
Las 7 Fases
| Fase | Duración | Actividades |
|---|---|---|
| 1. Descubrimiento | 1-2 días | Validar problema, investigar, descubrimientos |
| 2. Estrategia | 1 día | Hoja de ruta, hitos, decisiones |
| 3. Diseño | 2-3 días | Arquitectura, UX, especificaciones |
| 4. Desarrollo | Variable | TDD, implementación, iteración |
| 5. Calidad | 1-2 días | Testing, validación, rendimiento |
| 6. Lanzamiento | 1 día | Despliegue, documentación, release |
| 7. Crecimiento | Continuo | Monitoreo, feedback, iteración |
Transiciones de Fase
Cada fase requiere criterios de Avance/No-Avance:
## Fase [N] Completada
### Lista de Verificación Avance/No-Avance
- [ ] Todas las tareas de la fase completadas
- [ ] Entregables verificados
- [ ] Sin bloqueadores
- [ ] Listo para siguiente fase
**Decisión:** AVANZAR / NO-AVANZAR
**Motivo:** [por qué]
Des-escalamiento
Si después de la Estrategia el alcance es menor → des-escalar a /dc:rapido
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.
- 2d ago First seen · 50 lines · 13 tokens per session scan A f2f1d2f33838
completo is a command published in the GitHub repository doncheli/don-cheli-sdd (57 stars, last pushed 25d ago), licensed Apache-2.0. It adds 13 tokens to every session and 378 once invoked, about $0.0001 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
add-phase
Add phase to end of current milestone in roadmap.
insert-phase
Insert urgent work as decimal phase (e.g., 72.1) between existing phases.
remove-phase
Remove a future phase from roadmap and renumber subsequent phases.
research-phase
Research how to implement a phase (standalone — usually use /pbr:plan-phase instead).
reapply-patches
Reapply local modifications after a PBR update.
update
Update PBR to latest version with changelog display.