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/implementar)<a href="https://agentmods.dev/commands/doncheli/don-cheli-sdd/implementar"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/implementar/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/implementar"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/implementar.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.00019 | $0.01996 |
| Opus 5.5 | $0.00008 | $0.00798 |
| Sonnet 5.5 | $0.00004 | $0.00399 |
| Haiku 4.5 | $0.00002 | $0.00200 |
Grade A, and why
implementar 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.
How it starts
The opening of the file, as written. The whole thing — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dc:implementar
Objetivo
Ejecutar las tareas generadas por /dc:desglosar de forma automatizada, siguiendo el ciclo TDD (RED → GREEN → REFACTOR) dentro de un entorno Docker aislado, con checkpoints formalizados para intervención humana.
Adaptado del comando
speckit.implementde Specular. Mejorado con Taxonomía de Checkpoints de Get Shit Done (gsd-build/get-shit-done).
Uso
/dc:implementar @specs/features/<dominio>/<Feature>.tasks.md
/dc:implementar --fase <numero>
/dc:implementar --seco # Solo mostrar plan sin ejecutar
Comportamiento
- Leer archivo
.tasks.md - Verificar que Docker está disponible
- Verificar Nyquist — Validar mapeo tests↔requisitos (Puerta 5)
- Ejecutar tareas fase por fase con checkpoints
Flujo por Fase
┌─ Fase 1: Setup ───────────────────────────────┐
│ Crear archivos vacíos: modelos, servicios, │
│ repositorios, controladores, tests │
│ → Verificar: archivos existen │
└────────────────────────────────────────────────┘
│
┌─ Fase 2: Tests Unitarios (RED) ───────────────┐
│ Escribir tests que FALLAN │
│ → docker compose run --rm test │
│ → Verificar: tests existen y FALLAN (RED) │
└────────────────────────────────────────────────┘
│
┌─ Fase 3: Tests BDD/Integración (RED) ────────┐
│ Escribir tests BDD desde Gherkin │
│ → Aplicar patrones ISA (isa.yml) │
│ → docker compose run --rm test │
│ → Verificar: tests BDD existen y FALLAN │
└────────────────────────────────────────────────┘
│
┌─ Fase 4: Lógica de Negocio (GREEN) ──────────┐
│ Implementar código que hace pasar los tests │
│ → docker compose run --rm test │
│ → [DETECCIÓN STUBS] automática │
│ → Verificar: TODOS los tests PASAN (GREEN) │
└────────────────────────────────────────────────┘
│
┌─ Fase 5: Lint & Tipos ───────────────────────┐
│ → docker compose run --rm lint │
│ → Verificar: sin errores de lint/tipos │
└────────────────────────────────────────────────┘
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 · 228 lines · 19 tokens per session scan A f75db25eedea
implementar is a command published in the GitHub repository doncheli/don-cheli-sdd (57 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 1,996 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
validate-phase
Post-build quality gate. Identifies test gaps and spawns nyquist-auditor to fill them.
review
Verify the build matched the plan. Automated checks + walkthrough with you.
test
Generate tests for completed phase code. Detects test framework and targets key files.
verify-work
Validate built features through conversational UAT.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
test-gen
Generate comprehensive tests for a specified file with edge cases and error scenarios.