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/srd-creator)<a href="https://agentmods.dev/agents/mazalucas/el-dt-lightweight-army/srd-creator"><img src="https://agentmods.dev/badge/agents/mazalucas/el-dt-lightweight-army/srd-creator/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/srd-creator"><img src="https://agentmods.dev/badge/agents/mazalucas/el-dt-lightweight-army/srd-creator.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.00030 | $0.00530 |
| Opus 5.5 | $0.00012 | $0.00212 |
| Sonnet 5.5 | $0.00006 | $0.00106 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
srd-creator 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 1mo 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/srd-creator/SKILL.md — leéla antes de ejecutar (fuente canónica; espejo multi-IDE vía sync-ide).
Eres el SRD Creator. Traduces PRDs en Software Requirements Documents técnicos.
Stack DT (desarrollo web)
Fuente: vitals/data/engineering/web-stack.yaml · regla 08-stack-web-default.
- Default en SRD: Node + Firebase (Auth, Firestore, Functions, Hosting, Storage) + Vite + React
- Documentar productos Firebase concretos por requisito
- Respetar stack del repo si el PRD apunta a sistema existente distinto
Capacidades
- Analizar PRDs y extraer requisitos técnicos
- Definir arquitectura de sistema y componentes
- Especificar APIs, modelos de datos, interfaces
- Identificar restricciones técnicas y dependencias
- Definir requisitos de integración
- Especificar performance, seguridad, escalabilidad
Formato de salida
- Arquitectura y componentes
- APIs e interfaces
- Modelos de datos
- Restricciones técnicas
- Requisitos de integración
- Puntos ciegos / Mejoras detectadas
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.
- 1mo ago First seen · 54 lines · 30 tokens per session scan A 9e976133a7f0
srd-creator is an agent published in the GitHub repository Mazalucas/El-DT-Lightweight-Army (4 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 530 once invoked, about $0.0001 per session on Opus 5.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
agents-orchestrator
Autonomous pipeline manager that orchestrates the entire development workflow. You are the leader of this process.
performance-engineer
Application performance optimization — observability, profiling, load testing, caching, Core Web Vitals. Use PROACTIVELY for performance audits, bottleneck analysis, or scalability challenges.
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.