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/pocgit 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/poc)<a href="https://agentmods.dev/commands/doncheli/don-cheli-sdd/poc"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/poc.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.00017 | $0.02883 |
| Opus 5 | $0.00009 | $0.01442 |
| Sonnet 5 | $0.00003 | $0.00577 |
| Haiku 4.5 | $0.00002 | $0.00288 |
Grade A, and why
poc 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.
How it starts
The opening of the file, as written. The whole thing — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dc:poc
Objetivo
Iniciar una Prueba de Concepto (PoC) para validar viabilidad técnica, explorar soluciones o demostrar una idea antes de comprometer una implementación completa. El PoC tiene reglas relajadas: prioriza velocidad y aprendizaje sobre calidad de producción.
Uso
/dc:poc <descripción de lo que se quiere validar>
/dc:poc --hipotesis "<lo que quiero demostrar>"
/dc:poc --tiempo 2h # Limitar timebox (default: 4h)
/dc:poc --graduar # Convertir PoC exitoso en feature real
Cuándo Usar
| Situación | PoC | Rápido | Completo |
|---|---|---|---|
| "¿Se puede hacer X con esta librería?" | ✅ | ||
| "¿Este enfoque escala?" | ✅ | ||
| "Necesito una demo para el stakeholder" | ✅ | ||
| "Corregir bug en auth" | ✅ | ||
| "Implementar feature de pagos" | ✅ | ||
| "¿WebSockets o SSE para real-time?" | ✅ | ||
| "Migrar de REST a GraphQL, ¿vale la pena?" | ✅ |
Regla de oro: Si la pregunta empieza con "¿se puede...?", "¿funciona...?" o "¿vale la pena...?" → es un PoC.
Diferencias con Modo Rápido y Completo
| Aspecto | PoC | Rápido (N1) | Completo (N3) |
|---|---|---|---|
| Objetivo | Validar viabilidad | Entregar cambio | Entregar feature |
| Output | Aprendizaje + demo | Código de producción | Sistema completo |
| TDD | Opcional (solo tests de validación) | Obligatorio | Obligatorio |
| Coverage | Sin mínimo | ≥85% | ≥85% |
| Lint/Types | Relajado | Obligatorio | Obligatorio |
| Docs | Veredicto + hallazgos | Descripción PR | spec.md + tech.md |
| Código | Desechable (puede no mergearse) | Producción | Producción |
| Timebox | Fijo (default 4h) | Variable | Variable |
| Constitución | Solo Art. VII (Stop-Loss) | Completa | Completa |
| Stubs permitidos | Sí (con marcador) | No | No |
| Contrato UI | No | Si aplica | Si aplica |
Proceso (4 fases)
Fase 1: Hipótesis (10 min)
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 · 303 lines · 17 tokens per session scan A 31b4c0d324d7
poc is a command published in the GitHub repository doncheli/don-cheli-sdd (57 stars, last pushed 26d ago), licensed Apache-2.0. It adds 17 tokens to every session and 2,883 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
audit-quiz-coverage
Find quiz coverage gaps from recent guide/CHANGELOG/CC-releases changes and propose new questions.
explain
This command was migrated to a skill in Claude Code 2.1.3. See: examples/skills/explain/SKILL.md.
add-phase
Add phase to end of current milestone in roadmap.
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.