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/commands/mazalucas/el-dt-lightweight-army/bootstrap)<a href="https://agentmods.dev/commands/mazalucas/el-dt-lightweight-army/bootstrap"><img src="https://agentmods.dev/badge/commands/mazalucas/el-dt-lightweight-army/bootstrap/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/commands/mazalucas/el-dt-lightweight-army/bootstrap"><img src="https://agentmods.dev/badge/commands/mazalucas/el-dt-lightweight-army/bootstrap.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.00000 | $0.00159 |
| Opus 5 | $0.00000 | $0.00079 |
| Sonnet 5 | $0.00000 | $0.00032 |
| Haiku 4.5 | $0.00000 | $0.00016 |
Grade A, and why
bootstrap 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 6d 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
/bootstrap
Grupo: Framework DT En una frase: Usar El DT como base: promover al raíz y soltar el remoto del template. Cuándo: Arrancar un proyecto nuevo a partir del template. Quién: Cualquier operador del repo.
Ejecutá el skill dt-bootstrap — .cursor/skills/dt-bootstrap/ y .agents/skills/dt-bootstrap/.
Generado desde vitals/config/commands-meta.yaml — corré scripts/sync-commands-from-meta.sh.
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.
- 6d ago First seen · 19 lines · 0 tokens per session scan A ff71fd157330
bootstrap is a command published in the GitHub repository Mazalucas/El-DT-Lightweight-Army (4 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 159 tokens. 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-09-03.
Other commands, from other repositories
auto-sprint
Orchestrateur de sprint de bout en bout (démarrage -> décomposition -> validation -> implémentation -> PR -> CI -> revue -> rétro -> merge).
review
Préparation Sprint Review.
parallel
You are executing the /hydra:parallel command. Start multiple agents simultaneously in different worktrees.
sync-todos-to-github
Convert TodoWrite task list to GitHub plan issue (triggers automation).
ready-pr-in-review
Move a PR from Draft to Ready for Review, assign a reviewer, add labels, and sync the related Jira ticket to In Review with the correct assignee.
sync
Synchronize task status with git commits, ensuring consistency between version control and task tracking.