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 dt-setupgit 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/dt-setup)<a href="https://agentmods.dev/skills/mazalucas/el-dt-lightweight-army/dt-setup"><img src="https://agentmods.dev/badge/skills/mazalucas/el-dt-lightweight-army/dt-setup/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/dt-setup"><img src="https://agentmods.dev/badge/skills/mazalucas/el-dt-lightweight-army/dt-setup.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.00061 | $0.01085 |
| Opus 5.5 | $0.00024 | $0.00434 |
| Sonnet 5.5 | $0.00012 | $0.00217 |
| Haiku 4.5 | $0.00006 | $0.00109 |
Grade A, and why
dt-setup 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 29d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dt-setup
Setup multi-IDE, no destructivo. Dos modos; el agente elige según el command invocado y el contexto.
| Command | Modo default |
|---|---|
/bienvenida |
first-run — checklist markdown, sin Ruby obligatorio |
/setup |
repair — regenerar desde fuentes canónicas + dt-doctor |
Referencias: references/first-run-checklist.md · references/welcome-message.md · references/post-sync-pipeline.md
Fuente de verdad
Registro de IDEs: vitals/config/ide-targets.yaml. No hardcodear IDEs en este skill.
Modo A — first-run (default en /bienvenida)
El clone ya trae .cursor/, .agents/, .claude/, commands y skills en Git. El usuario no necesita Ruby para empezar.
- Resolver
git_root(multi-proyecto:vitals/workspace.yamlsi existe). - Seguir todo
references/first-run-checklist.md: verificar paths, Git, detectar drift, registrar dt-upstream si aplica (§4), e instalar el pre-push con./scripts/dt-oficial.sh install-hook. - No correr
sync-idenidt-doctorsalvo drift evidente y que el usuario pida reparar → pasar a modo B. - Entregar obligatoriamente el mensaje canónico en
references/welcome-message.md: completar placeholders tras checklist; si hay drift → rama/setupvisible en el mensaje (no solo al final). - Cierre obligatorio: "Siguiente paso:
/yo" — el mensaje de bienvenida ya incluye la tarjeta ritual; no acortar a una línea.
Registro dt-upstream (first-run)
Si el repo parece El DT (AGENTS.md + vitals/config/commands-meta.yaml) y existe origin y no existe remote dt-upstream:
-
Preguntar: ¿mantenés el repo canónico/plantilla o es consumidor?
-
Consumidor (default en clone antes de
/bootstrap):git remote add dt-upstream "$(git remote get-url origin)"
What ships with it
3 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.
- 29d ago Changed 4a50b0d2851f
- 1mo ago Changed · +1 lines dad22d845000
- 1mo ago First seen · 67 lines · 61 tokens per session scan A 9e185d482147
dt-setup is a skill published in the GitHub repository Mazalucas/El-DT-Lightweight-Army (4 stars, last pushed yesterday), licensed MIT. It adds 61 tokens to every session and 1,085 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…