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/aplicar)<a href="https://agentmods.dev/commands/doncheli/don-cheli-sdd/aplicar"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/aplicar.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.00011 | $0.00546 |
| Opus 5 | $0.00005 | $0.00273 |
| Sonnet 5 | $0.00002 | $0.00109 |
| Haiku 4.5 | $0.00001 | $0.00055 |
Grade A, and why
aplicar 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 4d 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:aplicar
Objetivo
Implementar las tareas de un cambio específico, con soporte para cambios paralelos y context switching.
Adaptado de
/opsx:applyde OpenSpec — implementación fluida con soporte multi-cambio.
Uso
/dc:aplicar # Implementar el cambio activo
/dc:aplicar <nombre-cambio> # Implementar un cambio específico
/dc:aplicar --continuar # Retomar donde se dejó
Diferencia con /dc:implementar
/dc:implementar |
/dc:aplicar |
|---|---|
| Trabaja con .tasks.md clásico | Trabaja con carpeta de cambio |
| Un cambio a la vez | Múltiples cambios en paralelo |
| Pipeline rígido | Flujo flexible |
| Sin context switching | Con context switching |
Comportamiento
- Leer
.dc/cambios/<nombre>/tareas.md - Detectar progreso previo (si hay tareas ya completadas)
- Ejecutar tareas pendientes una por una
- Ejecutar stop hooks después de cada fase
- Marcar tareas como completadas
- Reportar progreso
Output
=== Aplicando: agregar-dark-mode ===
Progreso: retomando desde tarea 3/8
✅ 1.1 Crear ThemeContext provider (ya hecho)
✅ 1.2 Crear hook useTheme (ya hecho)
✅ 2.1 Agregar CSS custom properties (ya hecho)
🔄 2.2 Crear componente ThemeToggle ← EN PROGRESO
→ Escribiendo tests...
→ Implementando componente...
→ Tests pasan ✅
⬜ 3.1 Integrar toggle en header
⬜ 3.2 Agregar localStorage persistence
⬜ 4.1 Dark mode para todas las páginas
⬜ 4.2 Transición suave entre temas
Progreso: 4/8 tareas completadas (50%)
Context Switching
# Trabajando en dark mode...
/dc:aplicar agregar-dark-mode # tarea 4/8
# Interrumpido por bug urgente
/dc:aplicar corregir-login # empieza desde tarea 1/3
# Bug corregido, volver a dark mode
/dc:aplicar agregar-dark-mode # retoma en tarea 5/8
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.
- 4d ago First seen · 74 lines · 11 tokens per session scan A 22ad7d980304
aplicar is a command published in the GitHub repository doncheli/don-cheli-sdd (57 stars, last pushed 28d ago), licensed Apache-2.0. It adds 11 tokens to every session and 546 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
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.
new-milestone
Start a new milestone cycle — update PROJECT.md and route to requirements.
add-todo
Capture idea or task as todo from current conversation context.
audit-milestone
Audit milestone completion against original intent before archiving.
backlog
Manage backlog items — ideas not ready for active planning. Add, review, promote, or remove.