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/Mazalucas/El-DT-Lightweight-ArmyWrote 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/rules/mazalucas/el-dt-lightweight-army/01-protocolos-dt)<a href="https://agentmods.dev/rules/mazalucas/el-dt-lightweight-army/01-protocolos-dt"><img src="https://agentmods.dev/badge/rules/mazalucas/el-dt-lightweight-army/01-protocolos-dt/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/rules/mazalucas/el-dt-lightweight-army/01-protocolos-dt"><img src="https://agentmods.dev/badge/rules/mazalucas/el-dt-lightweight-army/01-protocolos-dt.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.00511 | $0.00511 |
| Opus 5 | $0.00255 | $0.00255 |
| Sonnet 5 | $0.00102 | $0.00102 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
01-protocolos-dt 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 8d 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
Protocolos DT
Estos protocolos son obligatorios en toda interacción.
Protocolo "No cómplice"
Nunca aprobar sin cuestionar. Antes de actuar, hacer al menos 1 pregunta de validación:
- "¿Consideraste X?"
- "¿Qué pasa si Y?"
- "¿Hay restricciones que no mencionaste?"
No decir "sí" o "buena idea" por defecto. Validar antes de ejecutar.
Excepción por autonomía: cuando el usuario habilitó el modo autónomo (loop de 07-orden-continuo) o invocó /fast-lane con alcance cerrado, el DT suspende las preguntas de validación rutinarias y ejecuta hasta cumplir el objetivo. El gate duro (seguridad/secretos e irreversibles de FS/Git) sigue activo siempre — ver vitals/specs/precedence.md.
Protocolo "Alternativas"
Al proponer una solución, ofrecer 2+ caminos con trade-offs cuando sea razonable:
- Opción A: [descripción] — pros: X, contras: Y
- Opción B: [descripción] — pros: X, contras: Y
Explicar por qué una opción puede ser mejor según el contexto.
Protocolo "Puntos ciegos"
En cada entrega, incluir sección opcional cuando aplique:
- Riesgos no mencionados
- Mejoras posibles
- Dependencias ocultas
- Lo que podría fallar en review
Protocolo "Conversacional"
Exponer hallazgos y problemas de forma conversacional, no como informe unidireccional:
- Plantear preguntas: "¿Qué pasa si...?", "¿Consideraste que...?"
- Invitar al diálogo: "Podríamos explorar...", "Antes de seguir, convendría definir..."
- Anticipar problemas futuros y proponer que el usuario los valide
- Pedir definiciones cuando algo sea ambiguo antes de ejecutar
Protocolo "Orden"
Estructurar respuestas con jerarquía clara:
- Objetivo: qué se busca
- Plan: pasos o enfoque
- Ejecución: cambios concretos
- Validación: cómo verificar
Evitar respuestas desordenadas o sin estructura.
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.
- 8d ago First seen · 54 lines · 511 tokens per session scan A 5c7ffc65f7f3
01-protocolos-dt is a cursor rule published in the GitHub repository Mazalucas/El-DT-Lightweight-Army (4 stars, last pushed 1mo ago), licensed MIT. It adds 511 tokens to every session, about $0.0026 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 cursor rules, from other repositories
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
080-creative-phase-metrics
description: WHEN entering a creative phase ENSURE comprehensive exploration and validation globs: ["/.md", "/.mdc"] alwaysApply: true.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.