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 deploygit 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/deploy)<a href="https://agentmods.dev/skills/mazalucas/el-dt-lightweight-army/deploy"><img src="https://agentmods.dev/badge/skills/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/skills/mazalucas/el-dt-lightweight-army/deploy"><img src="https://agentmods.dev/badge/skills/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.00049 | $0.01156 |
| Opus 5.5 | $0.00020 | $0.00462 |
| Sonnet 5.5 | $0.00010 | $0.00231 |
| Haiku 4.5 | $0.00005 | $0.00116 |
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.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
deploy
Skill genérico: la primera vez descubre cómo se despliega este proyecto y materializa la config; las siguientes ejecuciones la siguen.
No confundir con: subagente devops (diseño de pipelines) · /github-save-small (release del template DT).
Pre-requisitos
- Sesión válida —
vitals/ops/session.yamlconoperator.id; si falta →/yo. - Working tree razonablemente limpio en paths de deploy (build artifacts no commiteados).
- Secretos nunca en el repo — Firebase Secrets, Cloud Run env, etc. (regla
90-seguridad-secrets).
Modo de operación
Leer vitals/config/deploy.yaml (plantilla: vitals/config/deploy.yaml.example).
| Estado | Acción |
|---|---|
Archivo ausente o initialized: false |
Bootstrap (sección abajo) — no ejecutar deploy real hasta confirmación |
initialized: true |
Ejecutar según deploy.yaml + references/project-deploy.md si existe |
Bootstrap — primera ejecución de /deploy
Objetivo: que la IA complete la skill con lo que este repo ya tiene (o debería tener).
-
Discover (solo lectura):
- Docs:
docs/DEPLOY.md,docs/**/deploy*.md, README sección deploy - Infra:
firebase.json,.firebaserc,Dockerfile,cloudbuild.yaml,.github/workflows/*deploy* - Scripts:
package.json(scripts.deploy*,scripts.build), monorepo enapps/*,frontend/,backend/ - Stack default DT:
vitals/data/engineering/web-stack.yaml· regla08-stack-web-default - Referencia Firebase: skill
devops→devops/references/firebase-deploy.md
- Docs:
-
Inferir plataforma principal (
firebase|cloud-run|vercel|docker|custom) y entornos (production,staging, …). -
Generar (pedir confirmación antes de escribir):
vitals/config/deploy.yaml— desde example,initialized: truetras OK del operador.cursor/skills/deploy/references/project-deploy.md— usar plantillareferences/project-deploy.template.md
What ships with it
2 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 · 82 lines · 49 tokens per session scan A 24a4ca35bf2f
deploy is a skill published in the GitHub repository Mazalucas/El-DT-Lightweight-Army (4 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 1,156 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…