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/archivar)<a href="https://agentmods.dev/commands/doncheli/don-cheli-sdd/archivar"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/archivar.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.00013 | $0.00534 |
| Opus 5 | $0.00006 | $0.00267 |
| Sonnet 5 | $0.00003 | $0.00107 |
| Haiku 4.5 | $0.00001 | $0.00053 |
Grade A, and why
archivar 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 4d 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:archivar
Objetivo
Sincronizar las specs delta (cambios incrementales) con las specs principales y archivar las features completadas para referencia futura.
Adaptado de
sdd-archivede Gentle-AI — fase de cierre que Don Cheli no tenía.
Uso
/dc:archivar @specs/features/<dominio>/<Feature>.feature
/dc:archivar --todo # Archivar todas las features @implementada
Comportamiento
- Verificar que la feature tiene tag
@implementada(todos los tests pasan) - Mover artefactos completados a
specs/archivo/ - Actualizar la spec principal del dominio si existe
- Registrar en
.dc/memoria/decisiones.md - Limpiar archivos temporales de la feature
Estructura de Archivo
specs/
├── features/ # Features ACTIVAS
│ └── usuario/
│ └── EditarPerfil.feature (en progreso)
├── archivo/ # Features COMPLETADAS
│ └── usuario/
│ └── CrearUsuario/
│ ├── CrearUsuario.feature
│ ├── CrearUsuario.plan.md
│ ├── CrearUsuario.tasks.md
│ ├── review.md
│ └── metadata.json # Fechas, métricas, estimado vs real
└── db_schema/ # Schemas (no se archivan)
metadata.json
{
"feature": "CrearUsuario",
"dominio": "usuario",
"archivada": "2026-03-21",
"iniciada": "2026-03-18",
"duracion_real_dias": 3,
"estimado_dias": 5,
"precision_estimado": "60%",
"escenarios_gherkin": 5,
"tests_totales": 12,
"archivos_modificados": 8
}
Valor para el Framework
Los datos archivados alimentan:
/dc:estimar→ datos históricos para estimados más precisos/dc:analizar-sesiones→ patrones de desarrollo- Memoria persistente → decisiones y convenciones aprendidas
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.
- 4d ago First seen · 70 lines · 13 tokens per session scan A 586d7a858f8f
archivar is a command published in the GitHub repository doncheli/don-cheli-sdd (57 stars, last pushed 28d ago), licensed Apache-2.0. It adds 13 tokens to every session and 534 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
insert-phase
Insert urgent work as decimal phase (e.g., 72.1) between existing phases.
remove-phase
Remove a future phase from roadmap and renumber subsequent phases.
add-todo
Capture idea or task as todo from current conversation context.
audit-milestone
Audit milestone completion against original intent before archiving.
new-milestone
Start a new milestone cycle — update PROJECT.md and route to requirements.
backlog
Manage backlog items — ideas not ready for active planning. Add, review, promote, or remove.