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 engineering-reusegit 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/engineering-reuse)<a href="https://agentmods.dev/skills/mazalucas/el-dt-lightweight-army/engineering-reuse"><img src="https://agentmods.dev/badge/skills/mazalucas/el-dt-lightweight-army/engineering-reuse/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/engineering-reuse"><img src="https://agentmods.dev/badge/skills/mazalucas/el-dt-lightweight-army/engineering-reuse.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.00062 | $0.00467 |
| Opus 5.5 | $0.00025 | $0.00187 |
| Sonnet 5.5 | $0.00012 | $0.00093 |
| Haiku 4.5 | $0.00006 | $0.00047 |
Grade A, and why
engineering-reuse 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)
Aplica los protocolos del Director Técnico: ordenar, cuestionar, alternativas, Puntos ciegos / Mejoras detectadas.
Cuándo usar
Siempre antes de escribir o proponer código ejecutable — solo o como subagente (arquitecto, frontend, devops, qa, remotion-producer).
Regla transversal: 15-engineering-reuse. Referencia humana: docs/03_reference/engineering-reuse-default.md (DOC-REF-006).
Jerarquía (memorizar)
repo existente → design system / lib del proyecto → primitivas del framework → nuevo (documentado)
Detalle: references/reuse-hierarchy.md.
Pipeline obligatorio
- Discover —
references/discover-before-create.mdpor capa (backend, UI, infra, tests, Remotion). - Decidir — extender vs componer vs crear (
references/reuse-hierarchy.md). - Implementar — diff mínimo; match convenciones del repo.
- Entregar —
references/deliverable-template.md(sección Qué reutilicé).
Anti-patterns
Ver references/anti-patterns.md. Señalar duplicación propuesta antes de implementar.
Evals
Casos de regresión: evals/evals.json.
Routing
| Pedido | Rol especializado |
|---|---|
| Solo arquitectura/spec backend | arquitecto (+ esta skill) |
| Solo UI | frontend (+ esta skill) |
| Solo CI/deploy | devops (+ esta skill) |
| Solo tests | qa (+ esta skill) |
| Solo Remotion | remotion-producer (+ esta skill) |
Esta skill complementa skills de rol; no las reemplaza.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 50 lines · 62 tokens per session scan A 6b0b256260dd
engineering-reuse is a skill published in the GitHub repository Mazalucas/El-DT-Lightweight-Army (4 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 467 once invoked, about $0.0002 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…