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/metricas)<a href="https://agentmods.dev/commands/doncheli/don-cheli-sdd/metricas"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/metricas/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/metricas"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/metricas.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.00011 | $0.00338 |
| Opus 5 | $0.00005 | $0.00169 |
| Sonnet 5 | $0.00002 | $0.00068 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
metricas 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 6d 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:metricas — Métricas en Terminal
Qué hace
Muestra un resumen compacto de las métricas SDD del proyecto directamente en la terminal.
Fuente de datos
Lee .dc/metrics.json que se actualiza automáticamente en cada sesión.
Output en terminal
═══════════════════════════════════════════
Don Cheli SDD — Métricas del Proyecto
═══════════════════════════════════════════
📊 Sesiones: 12 completadas (prom. 38 min)
✅ Quality Gates: 94% aprobación a la primera
🧪 TDD Acierto: 87% tests pasan al primer intento
📈 Cobertura: 91% (objetivo: 85%)
🔍 Stubs: 3 detectados, 3 eliminados
🛡️ OWASP: 0 críticos, 2 warnings
📐 Estimación: ±15% desviación promedio
Modelo más preciso: Planning Poker IA (±8%)
Feature más rápida: auth-jwt (1.2h vs 2h estimado)
═══════════════════════════════════════════
Subcomandos
/dc:metricas # Resumen completo
/dc:metricas --tdd # Solo métricas de TDD
/dc:metricas --owasp # Solo métricas de seguridad
/dc:metricas --estimados # Solo precisión de estimados
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.
- 6d ago First seen · 43 lines · 11 tokens per session scan A 2e2b6d40e674
metricas is a command published in the GitHub repository doncheli/don-cheli-sdd (57 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 338 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
review
Verify the build matched the plan. Automated checks + walkthrough with you.
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.
feature-implement-execute
Phase 4 of develop: Execute the implementation plan with per-task TDD, quality gates, and completion verification.
ccc-feature-start
Kickoff a new feature with branch creation, TDD setup, and task breakdown.