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/validar-specgit 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/validar-spec)<a href="https://agentmods.dev/commands/doncheli/don-cheli-sdd/validar-spec"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/validar-spec.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 | $0.00078 | $0.00736 |
| Opus 5 | $0.00039 | $0.00368 |
| Sonnet 5 | $0.00016 | $0.00147 |
| Haiku 4.5 | $0.00008 | $0.00074 |
Grade A, and why
validar-spec 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 yesterday.
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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dc:validar-spec
Objetivo
Ejecutar una validación multi-capa sobre las especificaciones ANTES de desglosar en tareas. Detecta problemas que /dc:clarificar no cubre: implementation leakage, measurability, completeness, y adherencia a la constitución del proyecto.
Inspirado en los 13 pasos de validación del framework BMAD.
Uso
/dc:validar-spec # Validar todas las specs activas
/dc:validar-spec @specs/features/auth/ # Validar un dominio
/dc:validar-spec --strict # Modo estricto (0 warnings permitidos)
Validaciones (8 checks)
| # | Check | Qué detecta | Severidad |
|---|---|---|---|
| 1 | Implementation Leakage | ¿La spec menciona tecnologías donde no debería? (WHAT vs HOW) | 🔴 Error |
| 2 | Measurability | ¿Los criterios de aceptación son medibles y verificables? | 🟠 Warning |
| 3 | Completeness | ¿Hay happy path + sad paths + edge cases para cada scenario? | 🔴 Error |
| 4 | Traceability | ¿Cada requisito tiene al menos un escenario que lo cubre? | 🔴 Error |
| 5 | Constitution Adherence | ¿La spec respeta los principios de constitucion-proyecto.md? | 🔴 Error |
| 6 | Consistency | ¿Hay contradicciones entre escenarios o entre features? | 🟠 Warning |
| 7 | Ambiguity | ¿Hay términos ambiguos o no definidos? (complementa clarificar) | 🟠 Warning |
| 8 | Scope Alignment | ¿La spec está dentro del alcance definido en la propuesta? | 🟠 Warning |
Output
📋 Validación de Spec: demo-sdd
✅ PASS: Implementation Leakage (0 violaciones)
✅ PASS: Completeness (todos los escenarios tienen happy + sad path)
⚠️ WARN: Measurability — 2 criterios sin umbral cuantificable
- VerPartidosEnVivo.feature:45 — "respuesta rápida" → ¿cuántos ms?
- PrediccionesIA.feature:32 — "precisión aceptable" → ¿qué porcentaje?
✅ PASS: Traceability (100% de requisitos cubiertos)
✅ PASS: Constitution Adherence
✅ PASS: Consistency
⚠️ WARN: Ambiguity — 1 término sin definir
- "usuario premium" usado en 3 features pero no definido en ninguna
✅ PASS: Scope Alignment
Resultado: ⚠️ PASA CON WARNINGS (2 warnings, 0 errores)
→ Corregir warnings antes de /dc:desglosar para máxima calidad
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.
- yesterday First seen · 59 lines · 78 tokens per session scan A e4044f3b945e
validar-spec is a command published in the GitHub repository doncheli/don-cheli-sdd (57 stars, last pushed 25d ago), licensed Apache-2.0. It adds 78 tokens to every session and 736 once invoked, about $0.0004 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
run
Implement SPEC requirements using DDD/TDD methodology.
add-phase
Add phase to end of current milestone in roadmap.
reapply-patches
Reapply local modifications after a PBR update.
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).
update
Update PBR to latest version with changelog display.