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/traspasar)<a href="https://agentmods.dev/commands/doncheli/don-cheli-sdd/traspasar"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/traspasar.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.00016 | $0.00633 |
| Opus 5 | $0.00008 | $0.00316 |
| Sonnet 5 | $0.00003 | $0.00127 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
traspasar 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dc:traspasar
Objetivo
Generar un documento de traspaso estructurado que permite a la siguiente sesión (o agente) retomar exactamente donde se dejó. Diferente de /dc:cerrar-sesion que es un checklist para ti — el traspaso es un documento escrito para el siguiente lector.
Adaptado de
session-handoffde Pro-Workflow.
Uso
/dc:traspasar
Output
# Traspaso de Sesión — 2026-03-21 16:45
## Estado
- **Branch:** feature/oauth-login
- **Commits esta sesión:** 3
- **Cambios sin commit:** 2 archivos
- **Tests:** ✅ pasando
## ✅ Completado
- Endpoint POST /api/auth/google
- Endpoint POST /api/auth/github
- 12 unit tests para ambos endpoints
- Middleware de validación de tokens OAuth
## 🔄 En Progreso
- Refresh token (src/services/auth/refresh.ts:23)
→ Falta implementar rotación de tokens
→ El test skeleton ya existe en tests/auth/refresh.test.ts
## ⬜ Pendiente
- [ ] Vincular OAuth a cuenta existente por email
- [ ] Revocar token al logout
- [ ] BLOQUEADO: Endpoint de callback necesita URL de producción
## 🧠 Decisiones Tomadas
- Elegido Strategy Pattern para providers (Google, GitHub)
→ Razón: extensible para Apple/Microsoft después
- Tokens JWT con 15min de vida + refresh de 7 días
→ Razón: balance seguridad/UX
## 📄 Archivos Tocados
- `src/services/auth/google.ts` — Provider de Google OAuth
- `src/services/auth/github.ts` — Provider de GitHub OAuth
- `src/middleware/oauth-validate.ts` — Validación de tokens
- `tests/auth/google.test.ts` — 6 tests
- `tests/auth/github.test.ts` — 6 tests
## ⚠️ Gotchas
- NextAuth v5 cambia la API: `getSession()` ahora es async
- El mock de Google no devuelve `refresh_token` en primer login
## ▶️ Comando de Retomar
> Continuar en branch `feature/oauth-login`. Implementar refresh token
> (src/services/auth/refresh.ts). El test skeleton ya está. Siguiente
> paso: implementar rotación de tokens en el endpoint POST /api/auth/refresh.
Guardrails
- Escribir para el lector — No para ti
- Incluir paths y líneas — Ser específico
- Comando de retomar copy-pasteable — 1-2 oraciones de contexto
- Solo hechos — Describir cambios funcionalmente, no inferir motivación
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 · 77 lines · 16 tokens per session scan A ba5d5730a851
traspasar is a command published in the GitHub repository doncheli/don-cheli-sdd (57 stars, last pushed 28d ago), licensed Apache-2.0. It adds 16 tokens to every session and 633 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
thread
Persistent context threads for cross-session work that spans phases. Lighter than pause/resume.
pause-work
Create context handoff when pausing work mid-phase.
pause
Save your current session state for later resumption.
retex
Retex - Capture lesson learned dans memory après fix, rollback, erreur.
evolve
A knowledge-review workflow that groups repeated lessons and turns them into reusable commands, automatic skills, or separate agents. A command is user-triggered, a skill is an automatic behaviour, and an agent handles a complex multi-step task.
status
A project-status command that checks a code repository and its supporting project notes. The supplied description is in Chinese and lists checks for Git, a memory bank, dependencies, environment settings, components, and conflicts.