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/07-orden-continuo)<a href="https://agentmods.dev/rules/mazalucas/el-dt-lightweight-army/07-orden-continuo"><img src="https://agentmods.dev/badge/rules/mazalucas/el-dt-lightweight-army/07-orden-continuo/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/07-orden-continuo"><img src="https://agentmods.dev/badge/rules/mazalucas/el-dt-lightweight-army/07-orden-continuo.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.00000 | $0.00298 |
| Opus 5 | $0.00000 | $0.00149 |
| Sonnet 5 | $0.00000 | $0.00060 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
07-orden-continuo 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
Orden continuo
Tras cambios que toquen docs/, reglas, commands, skills, vitals/specs/, vitals/config/ o estructura del repo:
- Ejecutar el cambio pedido.
- Una pasada de
./scripts/dt-doctor.sh. - Corregir hallazgos que no sean gate duro; si quedan pendientes, listarlos en Puntos ciegos.
- Loop completo (repetir hasta verde) solo si el usuario lo pide o el cambio es normativa DT mayor.
Orden en verde (DoD)
Frontmatter en docs · capa correcta · sync-catalog.rb · IDs en id-registry · enlaces válidos · paridad multi-IDE (sync-ide.sh --check) · pulse fresco si cambió VERSION.
Gate duro
Secretos nunca al repo · irreversibles FS/Git (force push, bootstrap) → confirmación humana. vitals/specs/precedence.md.
Herramientas
dt-doctor.sh · sync-catalog.rb · sync-ide.sh · sync-commands-from-meta.sh
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 · 27 lines · 0 tokens per session scan A 053fd52f1233
07-orden-continuo is a cursor rule published in the GitHub repository Mazalucas/El-DT-Lightweight-Army (4 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 298 tokens. 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
github-development-wf
Enforces structured development workflow using GitHub issues, milestones, and projects. Ensures systematic progression through milestone-focused development with comprehensive tracking and verification.
github-repo-triage
Triage and maintain GitHub repos — issues, PRs, cherry-picks, releases, publishing.
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.