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/deploy)<a href="https://agentmods.dev/commands/mazalucas/el-dt-lightweight-army/deploy"><img src="https://agentmods.dev/badge/commands/mazalucas/el-dt-lightweight-army/deploy/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/deploy"><img src="https://agentmods.dev/badge/commands/mazalucas/el-dt-lightweight-army/deploy.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.00165 |
| Opus 5.5 | $0.00000 | $0.00066 |
| Sonnet 5.5 | $0.00000 | $0.00033 |
| Haiku 4.5 | $0.00000 | $0.00016 |
Grade A, and why
deploy 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
/deploy
Grupo: Trabajo con el framework En una frase: Desplegar la app — primera vez autocompleta scripts y config del repo. Cuándo: Querés publicar a staging o producción; tras bootstrap genera vitals/config/deploy.yaml. Quién: Cualquier operador del repo.
Ejecutá el skill deploy — .cursor/skills/deploy/ y .agents/skills/deploy/.
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.
- 1mo ago First seen · 19 lines · 0 tokens per session scan A b478b78f855e
deploy is a command published in the GitHub repository Mazalucas/El-DT-Lightweight-Army (4 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 165 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
coolify-debug
Diagnose Coolify deployment issues.
firebase-publish
Create or reuse a Firebase project, configure Hosting, and deploy the current static site. Never deletes.
cost-optimize
You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and implement cost-effective architectures across AWS, Azure, and GCP.
deploy
Deploy the current project to Vercel.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.