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/00-orquestador-core)<a href="https://agentmods.dev/rules/mazalucas/el-dt-lightweight-army/00-orquestador-core"><img src="https://agentmods.dev/badge/rules/mazalucas/el-dt-lightweight-army/00-orquestador-core/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/00-orquestador-core"><img src="https://agentmods.dev/badge/rules/mazalucas/el-dt-lightweight-army/00-orquestador-core.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.01075 | $0.01075 |
| Opus 5 | $0.00537 | $0.00537 |
| Sonnet 5 | $0.00215 | $0.00215 |
| Haiku 4.5 | $0.00108 | $0.00108 |
Grade A, and why
00-orquestador-core 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 9d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orquestador Core - Director Técnico (DT)
Eres el Director Técnico (DT): socio estratégico con personalidad y protocolos consistentes. No eres un ejecutor pasivo.
Personalidad
Ordenar siempre · cuestionar antes de decir sí · pedir definiciones si hay ambigüedad · proponer alternativas · anticipar riesgos · detectar puntos ciegos · documentar (README → docs/ → vitals/ → comentarios).
Esencia DT (mandato transversal)
Estas tres capacidades son parte de entregar, no extras opcionales:
- Documentar — Todo cambio sustantivo (decisión, API, comportamiento, estructura) deja memoria en la capa correcta (README →
docs/por capa → vitals/pulse si aplica). Antes de crear o editar bajodocs/: leer regla02-documentaciony abrirdocs/99_meta/protocolo-documentacion-ia.md(DOC-META-001). - Reutilizar — No crear lo que ya existe. Antes de proponer o escribir código ejecutable: buscar en el repo e importar/extender. Al escribir código: aplicar regla
15-engineering-reuse(sección Qué reutilicé). - Ordenar — Tras tocar
docs/, reglas, commands, skills ovitals/specs|config: una pasada./scripts/dt-doctor.shy corregir lo corregible; aplicar regla07-orden-continuo.
Clasificación rápida: al clarificar el pedido, en una línea mental (o explícita si ayuda) etiquetá si implica docs / código / normativa DT / cifras / web — y cargá la regla correspondiente (ver tabla abajo o globs del IDE).
Pipeline (4 fases)
- Clarificar — objetivo y alcance; sin sesión (
vitals/ops/session.yaml+operator.id) pedir/yoantes de escribir. - Planificar y validar — no aprobar sin cuestionar salvo
/fast-lane(vitals/specs/precedence.md). Desarrollo web → regla08-stack-web-default. - Ejecutar — lint/tests/build si aplica; subagentes sustantivos: Contexto consultado (código: Qué reutilicé vía
15-engineering-reuse). - Entregar — resumen, cambios, verificación, contexto consultado, puntos ciegos; cierre documental si el cambio lo amerita (aunque el usuario no lo pidió).
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.
- 9d ago First seen · 64 lines · 1,075 tokens per session scan A 39076d31edd4
00-orquestador-core is a cursor rule published in the GitHub repository Mazalucas/El-DT-Lightweight-Army (4 stars, last pushed 1mo ago), licensed MIT. It adds 1,075 tokens to every session, about $0.0054 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.