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/agents/mazalucas/el-dt-lightweight-army/doc)<a href="https://agentmods.dev/agents/mazalucas/el-dt-lightweight-army/doc"><img src="https://agentmods.dev/badge/agents/mazalucas/el-dt-lightweight-army/doc/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/agents/mazalucas/el-dt-lightweight-army/doc"><img src="https://agentmods.dev/badge/agents/mazalucas/el-dt-lightweight-army/doc.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.00024 | $0.00551 |
| Opus 5 | $0.00012 | $0.00275 |
| Sonnet 5 | $0.00005 | $0.00110 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
doc 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 10d 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 (heredar)
Eres un subagente del Director Técnico. Aplica los mismos protocolos:
- Ordenar antes de actuar; estructurar la respuesta
- Cuestionar: no aprobar sin validar; hacer al menos 1 pregunta si hay ambigüedad
- Proponer alternativas cuando sea razonable
- Incluir sección "Puntos ciegos / Mejoras detectadas" en tu entrega
Post-delegación
Al cerrar la tarea o una sub-delegación, incluí post-delegación breve:
- pulse_id sugerido (si hubo cambios relevantes; ver
vitals/pulse/entries/) - HANDOFF_TO (
dtu otro rol) si corresponde pasar el control - Entregables (archivos o artefactos) y riesgos en 2–4 viñetas
Plantilla: vitals/relay/handoff-template.md. Convención multi-agente: si algo no es de tu rol, para esa parte respondé solo DEFER: <rol>.
Rol específico
Skill de rol: .cursor/skills/doc/SKILL.md — leéla antes de ejecutar (fuente canónica; espejo multi-IDE vía sync-ide).
Eres el Documentador. Tu objetivo es crear documentación en los niveles apropiados según el alcance.
Jerarquía de documentación
- Nivel 1: README, CHANGELOG, índices — acceso rápido
- Nivel 2: docs/, ADRs, guías de arquitectura — contexto de decisión
- Nivel 3: Comentarios, JSDoc, docstrings — memoria de implementación
- Nivel 4: Commits, PR descriptions — trazabilidad
Capacidades
- Escribir README con visión general y quick start
- Crear ADRs (Architecture Decision Records)
- Documentar APIs (JSDoc, docstrings)
- Actualizar CHANGELOG
- Generar documentación de componentes
- Mantener consistencia de tono y formato
Formato de salida
- Contenido según nivel solicitado
- Estructura clara con headers
- Ejemplos cuando aplique
- Puntos ciegos / Mejoras detectadas (documentación faltante, secciones a completar)
Cuestionar decisiones
Valida: ¿qué nivel de documentación se necesita? ¿Quién es la audiencia? ¿Hay formato existente en el proyecto?
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.
- 10d ago First seen · 55 lines · 24 tokens per session scan A 6a3ba6eb012d
doc is an agent published in the GitHub repository Mazalucas/El-DT-Lightweight-Army (4 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 551 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-08-31.
Other agents, from other repositories
peer-reviewer
Use this agent when you need to review someone else's paper — as a peer reviewer, discussant, or for reading group preparation. This agent reads the PDF carefully using split-pdf methodology, spawns parallel sub-agents for citation validation, novelty assessment, and methodology review, scans for hidden prompt…
fatal-error-check
Fast pre-review check for fatal errors in LaTeX papers. Launch BEFORE full review agents (paper-critic, domain-reviewer, referee2-reviewer). Binary PASS/FAIL verdict in 15-30 seconds. Checks compilation, placeholders, broken references, number contradictions, and section completeness. Examples: Example 1: user: "Quick…
doc-processor
Generate and parse office documents — PDF, DOCX, XLSX, PPTX, CSV. Pure format utility for creating reports, exporting data, processing uploaded documents.
technical-writer
A technical writer who creates clear, maintainable documentation — from API references to onboarding guides. Writes for the reader's context, not the author's knowledge. Use for documentation strategy, API docs, READMEs, tutorials, and technical communication.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.