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.
npx agentmods add commands/doncheli/don-cheli-sdd/capturargit 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/capturar)<a href="https://agentmods.dev/commands/doncheli/don-cheli-sdd/capturar"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/capturar.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.00677 |
| Opus 5 | $0.00037 | $0.00338 |
| Sonnet 5 | $0.00015 | $0.00135 |
| Haiku 4.5 | $0.00007 | $0.00068 |
Grade A, and why
capturar 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 2d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dc:capturar
Objetivo
Fire-and-forget de ideas durante cualquier fase de trabajo. Permite anotar pensamientos, bugs, mejoras o dudas sin pausar la tarea actual. El sistema clasifica automáticamente cada captura.
Uso
/dc:capturar "Deberíamos agregar rate limiting en el login"
/dc:capturar --tipo bug "El endpoint /users devuelve 500 con deviceId vacío"
/dc:capturar --listar
/dc:capturar --procesar
Clasificación Automática
Cada captura se clasifica en una de 5 categorías:
| Categoría | Emoji | Criterio | Acción |
|---|---|---|---|
quick-task |
⚡ | Resoluble en < 5 min, sin impacto en tarea actual | Ejecutar al terminar tarea actual |
inject |
💉 | Relevante para la tarea en curso | Incorporar al slice actual |
defer |
📋 | Importante pero no urgente | Agregar al backlog |
replan |
🔄 | Cambia el alcance o la estrategia | Pausar y replantear |
note |
📝 | Observación o aprendizaje | Guardar en conocimiento.md |
Comportamiento
- Capturar — Agregar entrada a
.dc/capturas.mdcon timestamp y clasificación - No interrumpir — La tarea actual continúa sin pausa
- Procesar — Al completar la tarea actual (o con
--procesar), revisar capturas pendientes - Clasificar — El LLM clasifica automáticamente basándose en el contexto actual
- Ejecutar — Las
quick-taskse ejecutan inmediatamente; lasinjectse incorporan al plan
Archivo de Capturas
# Capturas
## Pendientes
- [2026-03-22 14:30] ⚡ `quick-task` — Agregar rate limiting en login
- [2026-03-22 14:45] 📋 `defer` — Evaluar Sportmonks como segundo provider
- [2026-03-22 15:10] 💉 `inject` — El test de notifications.worker necesita mock de Expo SDK
## Procesadas
- [2026-03-22 13:00] 📝 `note` — Redis KEYS bloquea en producción → usar SCAN ✅
Integración con Pipeline
- Durante
/dc:implementar: las capturas se revisan al final de cada tarea - Durante
/dc:revisar: las capturas tipodeferse incluyen como observaciones - Con
/dc:cerrar-sesion: las capturas pendientes se transfieren al traspaso
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.
- 2d ago First seen · 62 lines · 74 tokens per session scan A 637834e9186e
capturar is a command published in the GitHub repository doncheli/don-cheli-sdd (57 stars, last pushed 26d ago), licensed Apache-2.0. It adds 74 tokens to every session and 677 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
add-todo
Capture idea or task as todo from current conversation context.
thread
Persistent context threads for cross-session work that spans phases. Lighter than pause/resume.
note
Zero-friction idea capture. Append, list, or promote notes to todos.
resume-work
Resume work from previous session with full context restoration.
resume
Pick up where you left off. Restores context and suggests next action.
statusline
Install or configure the PBR status line in Claude Code.