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/gategit 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/gate)<a href="https://agentmods.dev/commands/doncheli/don-cheli-sdd/gate"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/gate.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.00010 | $0.00513 |
| Opus 5 | $0.00005 | $0.00257 |
| Sonnet 5 | $0.00002 | $0.00103 |
| Haiku 4.5 | $0.00001 | $0.00051 |
Grade A, and why
gate 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.
What it actually says
/dc:gate — Custom Quality Gates
Subcomandos
/dc:gate crear <nombre>
Crear un nuevo quality gate custom en .dc/gates/:
- Preguntar: nombre descriptivo, tipo (grep o script), severidad (block o warn)
- Generar archivo YAML en
.dc/gates/<nombre>.yml - Ejecutar el gate para verificar que funciona
/dc:gate listar
Listar todos los gates custom del proyecto:
- Leer
.dc/gates/*.yml - Mostrar tabla: nombre, tipo, severidad, estado (activo/desactivado)
/dc:gate ejecutar [nombre]
Ejecutar gates custom:
- Si se pasa nombre: ejecutar solo ese gate
- Sin nombre: ejecutar todos los gates en
.dc/gates/ - Mostrar resultado por gate con ✅/⚠️/❌
- Resumen final: X pasaron, Y fallaron, Z advertencias
/dc:gate ci
Generar workflow de CI/CD para el proyecto actual:
- Detectar plataforma (GitHub Actions / GitLab CI)
- Copiar template desde
examples/ci/adaptado al proyecto - Incluir custom gates si existen
Formato de gate custom
name: Nombre descriptivo
type: grep | script
pattern: "regex" # Solo para type: grep
files: "src/**/*.ts" # Solo para type: grep
severity: block | warn
message: "Mensaje al fallar"
run: | # Solo para type: script
comando a ejecutar
Severidad
block— Falla la puerta, bloquea el mergewarn— Advertencia, no bloquea (configurable confail-on-warn)
Ejemplos incluidos
Ver examples/gates/ para 5 gates pre-configurados:
no-console-log.yml— Prohibir console.log en producciónno-any-typescript.yml— Evitar tipoanyen TypeScriptno-hardcoded-secrets.yml— Detectar secretos hardcodeadosmax-file-lines.yml— Archivos de máximo 300 líneasrequire-error-handling.yml— Manejo de errores en async
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 · 63 lines · 10 tokens per session scan A f8f53fe4f9b6
gate is a command published in the GitHub repository doncheli/don-cheli-sdd (57 stars, last pushed 26d ago), licensed Apache-2.0. It adds 10 tokens to every session and 513 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
land-and-deploy
This command was migrated to a skill in Claude Code 2.1.3. See: examples/skills/land-and-deploy/SKILL.md.
review-pr-ci
Non-interactive PR review for CI/CD context. Read-only analysis — no edits.
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.