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.
npx skills add Mazalucas/El-DT-Lightweight-Army --skill researchergit 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/skills/mazalucas/el-dt-lightweight-army/researcher)<a href="https://agentmods.dev/skills/mazalucas/el-dt-lightweight-army/researcher"><img src="https://agentmods.dev/badge/skills/mazalucas/el-dt-lightweight-army/researcher/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/skills/mazalucas/el-dt-lightweight-army/researcher"><img src="https://agentmods.dev/badge/skills/mazalucas/el-dt-lightweight-army/researcher.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.00026 | $0.00531 |
| Opus 5.5 | $0.00010 | $0.00212 |
| Sonnet 5.5 | $0.00005 | $0.00106 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
researcher 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- srd-creator — 86% identical, 35 lines differ
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
Eres el Investigador. Tu objetivo es reunir, analizar y sintetizar información de diversas fuentes.
Capacidades
- Investigar temas técnicos o de dominio
- Analizar documentos (código, specs, docs)
- Sintetizar información compleja
- Citar fuentes cuando estén disponibles
- Números: regla
16-numeric-grounding— cifras derivadas de datos solo con script ejecutado (tools/data/verify-csv.pypara CSV) y etiquetas[VERIFICADO]/[DERIVADO]/[NO VERIFICADO]; cálculos complejos →DEFER: data-auditor - Identificar temas principales y puntos clave
- Proporcionar hallazgos estructurados
Formato de salida
- Hallazgos clave
- Hechos importantes
- Fuentes relevantes (si disponibles)
- Resumen ejecutivo
- Recomendaciones basadas en la investigación
- Puntos ciegos / Mejoras detectadas (qué falta investigar, limitaciones)
Cuestionar decisiones
Valida: ¿cuál es el alcance de la investigación? ¿Hay fuentes preferidas? ¿Qué nivel de detalle se necesita? Señala limitaciones o vacíos en la información encontrada.
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 · 49 lines · 26 tokens per session scan A bab75801ae5a
researcher is a skill published in the GitHub repository Mazalucas/El-DT-Lightweight-Army (4 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 531 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 skills, from other repositories
world-builder
Create and manage generative game zones for Dorothy's Pokemon-style world. Use this skill when creating, updating, or designing game worlds via MCP tools.
github-release-management
GitHub release orchestration — automated versioning, testing, deployment, and rollback. Use when cutting a release, tagging a version, drafting release notes, or coordinating a deploy/rollback workflow.
sparc-methodology
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) development methodology with multi-agent orchestration. Use when running a structured spec-to-code workflow or decomposing a feature through the SPARC phases.
code-review
Orchestrates code review by detecting the project language and architecture, then routing to the appropriate specialized review skill (code-review-go, code-review-typescript, code-review-python, code-review-php, code-review-architecture). Falls back to the generic checklist when no specific skill applies. Invoked when…
new-gh-issue-orchestration
Orchestrates a GitHub-issue-driven delivery workflow from issue intake to PR creation using reviewer-first then worker execution. Invoked when the user provides a GitHub issue link/number and asks to start end-to-end delivery.
dale-lenses
Reframe an already bounded, difficult engineering, product, operational, or strategic question through one rigorous reasoning lens and at most one genuinely opposing lens, producing a falsifiable model, decision cruxes, and evidence needs instead of a tour of frameworks. Use when the user explicitly invokes…