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/audit-trail)<a href="https://agentmods.dev/commands/doncheli/don-cheli-sdd/audit-trail"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/audit-trail.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.00074 | $0.01613 |
| Opus 5 | $0.00037 | $0.00807 |
| Sonnet 5 | $0.00015 | $0.00323 |
| Haiku 4.5 | $0.00007 | $0.00161 |
Grade A, and why
audit-trail 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 5d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dc:audit-trail
Objetivo
Registrar, almacenar y consultar todas las decisiones asistidas por IA durante el ciclo de vida del proyecto: qué se generó, qué se aprobó, qué se modificó y por quién. Proporciona trazabilidad completa para auditorías, revisiones y post-mortems.
Uso
/dc:audit-trail # Ver entradas recientes (últimas 20)
/dc:audit-trail --registrar # Registrar acción actual
/dc:audit-trail --filtro accion=generate # Filtrar por tipo de acción
/dc:audit-trail --filtro artefacto=spec # Filtrar por tipo de artefacto
/dc:audit-trail --filtro fecha=2026-03-28 # Filtrar por fecha
/dc:audit-trail --exportar csv # Exportar como CSV
/dc:audit-trail --resumen # Estadísticas del proyecto
Comportamiento
1. REGISTRAR — Capturar entrada en el log
├── Timestamp UTC con timezone local
├── Tipo de acción: generate | approve | modify | reject | review
├── Artefacto afectado: spec | test | code | review | plan | config
├── Resumen (≤ 120 chars) de qué se hizo
├── Actor: ia | human | ci
└── Referencia a archivo o PR si aplica
2. ALMACENAR — Persistir en .dc/audit-trail.md
├── Formato Markdown + YAML front-matter por entrada
├── Append-only (nunca modificar entradas existentes)
└── Rotar archivo cuando supere 5,000 líneas → audit-trail-archive/
3. CONSULTAR — Filtrar y mostrar entradas
├── Soportar filtros combinables por fecha, acción y artefacto
├── Paginación: 20 entradas por página
└── Modo resumen: estadísticas agregadas
Estructura de Entrada
---
id: AT-0047
timestamp: 2026-03-28T14:32:11-03:00
action: generate # generate | approve | modify | reject | review
artifact: spec # spec | test | code | review | plan | config
actor: ia # ia | human | ci
summary: "Generado spec Gherkin para feature ReembolsosParciales (3 escenarios)"
ref: specs/features/pagos/reembolsos.feature
session: dc-session-2026-03-28-a
---
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.
- 5d ago First seen · 136 lines · 74 tokens per session scan A f1452b3ce8ff
audit-trail is a command published in the GitHub repository doncheli/don-cheli-sdd (57 stars, last pushed 29d ago), licensed Apache-2.0. It adds 74 tokens to every session and 1,613 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
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.