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/dashboard)<a href="https://agentmods.dev/commands/doncheli/don-cheli-sdd/dashboard"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/dashboard/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/dashboard"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/dashboard.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.00014 | $0.00394 |
| Opus 5.5 | $0.00006 | $0.00158 |
| Sonnet 5.5 | $0.00003 | $0.00079 |
| Haiku 4.5 | $0.00001 | $0.00039 |
Grade A, and why
dashboard 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.
What it actually says
/dc:dashboard — Dashboard de Métricas SDD
Qué hace
Genera un archivo dashboard.html interactivo con las métricas acumuladas del proyecto.
Fuente de datos
Lee .dc/metrics.json que se actualiza automáticamente al cerrar cada sesión.
Métricas que muestra
Eficiencia del pipeline
- Tiempo por fase: Promedio de duración de cada fase (Especificar → Revisar)
- Quality Gates: Tasa de aprobación (primera vez vs reintentos)
- Stubs detectados: Cuántos stubs fantasma se encontraron y eliminaron
TDD
- Tasa de acierto: Tests que pasaron al primer intento vs reintentos
- Cobertura por feature: Evolución de cobertura por sesión
- RED→GREEN ratio: Cuántos ciclos TDD se completaron
Estimaciones
- Precisión: Estimado vs real por feature (desviación %)
- Modelo más preciso: Cuál de los 4 modelos acertó más
Seguridad
- Hallazgos OWASP: Por categoría y severidad
- Tendencia: Hallazgos por sesión (debería decrecer)
Sesiones
- Total de sesiones: Completadas y promedio de duración
- Productividad: Features completadas por sesión
Output
.dc/dashboard.html — Dashboard HTML standalone (abrir en navegador)
.dc/metrics.csv — Export CSV para reporting corporativo
Ejecución
/dc:dashboard # Genera dashboard.html
/dc:dashboard --abrir # Genera y abre en navegador
/dc:dashboard --csv # Solo exporta CSV
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 · 53 lines · 14 tokens per session scan A 759def2251a8
dashboard is a command published in the GitHub repository doncheli/don-cheli-sdd (57 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 394 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
test
Generate tests for completed phase code. Detects test framework and targets key files.
validate-phase
Post-build quality gate. Identifies test gaps and spawns nyquist-auditor to fill them.
verify-work
Validate built features through conversational UAT.
review
Verify the build matched the plan. Automated checks + walkthrough with you.
feature-implement-execute
Phase 4 of develop: Execute the implementation plan with per-task TDD, quality gates, and completion verification.
ccc-feature-start
Kick off a feature: research context, create an isolated branch, confirm a green baseline, write a task breakdown, and the first failing test. Use when starting new feature work in a git repository.