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/debate)<a href="https://agentmods.dev/commands/doncheli/don-cheli-sdd/debate"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/debate/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/debate"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/debate.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.00088 | $0.01555 |
| Opus 5.5 | $0.00035 | $0.00622 |
| Sonnet 5.5 | $0.00018 | $0.00311 |
| Haiku 4.5 | $0.00009 | $0.00155 |
Grade A, and why
debate 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dc:debate
Objetivo
Invocar una deliberación entre múltiples perspectivas en conflicto sobre una decisión técnica, de producto o de negocio. Diferente de brainstorming (generar ideas) y de mesa-redonda (explorar opciones): el debate busca TENSIÓN entre roles senior para sacar a la luz riesgos que un solo agente no genera.
Inspirado en el "Party Mode" del framework BMAD.
Uso
/dc:debate "¿Monolito o microservicios para el MVP?"
/dc:debate "¿PostgreSQL o MongoDB para este caso de uso?"
/dc:debate --roles "CPO,Arquitecto,UX,Negocio"
Comportamiento
- Definir la pregunta y los roles participantes (default: CPO, Arquitecto, UX)
- Cada rol presenta su posición con argumentos concretos, datos y experiencia
- Cada rol critica las posiciones de los demás (adversarial)
- Se identifican los puntos de tensión irresolubles
- Se documenta la decisión con trade-offs explícitos
- Se guarda en
.dc/decisiones.md
Roles Disponibles
Roles de Negocio y Producto (Senior)
| Rol | Perspectiva | Prioriza |
|---|---|---|
| CPO (Chief Product Officer) | Visión de producto, estrategia y mercado | Product-market fit, roadmap, priorización basada en impacto, métricas de adopción |
| UX Lead | Experiencia de usuario y diseño | Usabilidad, accesibilidad (WCAG), research con usuarios, design systems, conversion funnels |
| Negocio (VP/Director) | Viabilidad comercial y estrategia | ROI, unit economics, time to revenue, ventaja competitiva, riesgos regulatorios |
Roles Técnicos (Senior)
| Rol | Perspectiva | Prioriza |
|---|---|---|
| Arquitecto | Sistema y escalabilidad | Mantenibilidad, performance, extensibilidad, deuda técnica |
| QA Lead | Calidad y testing | Testability, edge cases, regression, automatización |
| Seguridad (CISO) | Protección y compliance | OWASP, datos sensibles, auth, regulaciones (GDPR, SOC2) |
| DevOps | Operaciones y deploy | Observabilidad, CI/CD, costos infra, SLAs |
| DBA | Datos y persistencia | Consistencia, queries, migraciones, backup/recovery |
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 · 120 lines · 88 tokens per session scan A fbd44693a98e
debate is a command published in the GitHub repository doncheli/don-cheli-sdd (57 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 88 tokens to every session and 1,555 once invoked, about $0.0004 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
research-phase
Research how to implement a phase (standalone — usually use /pbr:plan-phase instead).
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.
reapply-patches
Reapply local modifications after a PBR update.
remove-phase
Remove a future phase from roadmap and renumber subsequent phases.
join-discord
Join the PBR Discord community.