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/time-travel)<a href="https://agentmods.dev/commands/doncheli/don-cheli-sdd/time-travel"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/time-travel/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/time-travel"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/time-travel.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.00078 | $0.01493 |
| Opus 5 | $0.00039 | $0.00746 |
| Sonnet 5 | $0.00016 | $0.00299 |
| Haiku 4.5 | $0.00008 | $0.00149 |
Grade A, and why
time-travel 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 7d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dc:time-travel — Debugging del Razonamiento
Objetivo
Visualizar el historial completo de razonamiento del framework: qué modelo se eligió, por qué, qué alternativas se descartaron, y cómo ajustar las decisiones futuras.
Uso
/dc:time-travel # Ver historial completo de la sesión
/dc:time-travel --fase planificar # Ver razonamiento de una fase específica
/dc:time-travel --decision T003 # Por qué se tomó una decisión en tarea T003
/dc:time-travel --modelo # Por qué se eligió cada modelo (haiku/sonnet/opus)
/dc:time-travel --ajustar # Modo interactivo para ajustar skills
Qué registra
Cada vez que el framework toma una decisión, registra en .dc/reasoning-log.json:
{
"session": "2026-04-06-001",
"decisions": [
{
"id": "D001",
"timestamp": "2026-04-06T10:15:00Z",
"phase": "comenzar",
"decision": "Nivel de complejidad detectado: 2 — Estándar",
"reasoning": "Múltiples archivos (8 estimados), 2 endpoints nuevos, 1 modelo de datos. No califica como Micro (1-3 archivos) ni Complejo (multi-módulo).",
"alternatives_considered": [
{ "option": "Nivel 1 — Micro", "rejected_because": "Más de 3 archivos estimados" },
{ "option": "Nivel 3 — Complejo", "rejected_because": "Un solo módulo, sin dependencias cross-módulo" }
],
"confidence": 0.85,
"model_used": "sonnet",
"model_reasoning": "Tarea de clasificación estándar, no requiere opus"
},
{
"id": "D002",
"timestamp": "2026-04-06T10:16:30Z",
"phase": "especificar",
"decision": "Usar /razonar:pre-mortem antes de generar specs",
"reasoning": "Feature involucra pagos. Pre-mortem detecta fallos potenciales antes de comprometer la arquitectura.",
"alternatives_considered": [
{ "option": "/razonar:primeros-principios", "rejected_because": "El dominio es bien conocido, no requiere descomposición fundamental" },
{ "option": "Sin razonamiento", "rejected_because": "Feature de alto riesgo (pagos), siempre aplicar razonamiento" }
],
"confidence": 0.92,
"skill_triggered": "razonamiento",
"model_used": "sonnet"
}
]
}
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.
- 7d ago First seen · 143 lines · 78 tokens per session scan A e79ec33a88a1
time-travel is a command published in the GitHub repository doncheli/don-cheli-sdd (57 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 78 tokens to every session and 1,493 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
forensics
Post-mortem investigation for failed or stuck workflows. Analyzes git history and planning artifacts.
audit-fix
Run audit, prioritize findings, auto-fix via quick tasks, test, and commit.
debug
Systematic debugging with hypothesis testing. Persistent across sessions.
scan
Analyze an existing codebase. Maps structure, architecture, conventions, and concerns.
optimize
Suggest concrete performance improvements for the given file or directory.
fix-issue
A command that takes a GitHub Issue—a tracked bug, request, or question—and guides its fix from investigation through testing and submission. TDD means writing a failing test first, then changing the code until the test passes.