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/pseudocodigo)<a href="https://agentmods.dev/commands/doncheli/don-cheli-sdd/pseudocodigo"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/pseudocodigo.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.00080 | $0.00499 |
| Opus 5 | $0.00040 | $0.00249 |
| Sonnet 5 | $0.00016 | $0.00100 |
| Haiku 4.5 | $0.00008 | $0.00050 |
Grade A, and why
pseudocodigo 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.
What it actually says
/dc:pseudocodigo
Objetivo
Crear un artefacto de pseudocódigo de alto nivel entre la fase de especificación y la planificación técnica. Fuerza al agente a razonar sobre la LÓGICA del sistema sin comprometer stack, framework o estructura de archivos.
Inspirado en la fase "P" (Pseudocode) del framework SPARC.
Uso
/dc:pseudocodigo # Desde las specs del sprint actual
/dc:pseudocodigo @specs/auth/ # Para un dominio específico
Comportamiento
- Leer las specs Gherkin del dominio
- Extraer los flujos principales (happy path + sad paths)
- Generar pseudocódigo agnóstico:
- Sin nombres de funciones reales
- Sin imports ni frameworks
- Sin tipos de datos específicos del lenguaje
- Solo lógica: CUANDO/SI/SINO/PARA-CADA/RETORNAR
- Identificar invariantes (condiciones siempre verdaderas)
- Listar casos límite y dependencias de datos
- Guardar en
.dc/pseudocodigo.md
Por qué existe
Sin pseudocódigo, el agente salta de "qué hacer" (spec) a "cómo implementar" (plan técnico) sin pasar por "qué lógica necesito". Esto causa:
- Sobre-ingeniería (resolver problemas que no existen)
- Under-ingeniería (olvidar edge cases obvios)
- Acoplamiento temprano a un framework
El pseudocódigo es el "boceto" del arquitecto antes de los planos.
Integración en el Pipeline
especificar → clarificar → PSEUDOCÓDIGO → planificar-tecnico → desglosar → implementar
Es opcional pero recomendado para tareas de complejidad ≥ 2 (Estándar).
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 · 50 lines · 80 tokens per session scan A 0e0e42b3cdfa
pseudocodigo is a command published in the GitHub repository doncheli/don-cheli-sdd (57 stars, last pushed 28d ago), licensed Apache-2.0. It adds 80 tokens to every session and 499 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-phase
Add phase to end of current milestone in roadmap.
remove-phase
Remove a future phase from roadmap and renumber subsequent phases.
research-phase
Research how to implement a phase (standalone — usually use /pbr:plan-phase instead).
reapply-patches
Reapply local modifications after a PBR update.
add-todo
Capture idea or task as todo from current conversation context.
audit-milestone
Audit milestone completion against original intent before archiving.