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/rules/mazalucas/el-dt-lightweight-army/40-devops)<a href="https://agentmods.dev/rules/mazalucas/el-dt-lightweight-army/40-devops"><img src="https://agentmods.dev/badge/rules/mazalucas/el-dt-lightweight-army/40-devops.svg" alt="Measured on agentmods" 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.00462 |
| Opus 5 | $0.00000 | $0.00231 |
| Sonnet 5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
40-devops 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 4d 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
DevOps e infraestructura
Stack default del DT: ver regla 08-stack-web-default · deploy Firebase. Reuse-first: 15-engineering-reuse · DOC-REF-006 · skill devops.
Principios
- IaC declarativo — workflows,
firebase.json, Terraform/Pulumi versionados - DRY en pipelines — extender jobs/workflows existentes; matrices y reusable workflows antes de duplicar YAML
- Secrets nunca en YAML — Firebase Secrets, GitHub Secrets, secret managers del cloud
- Un script canónico — preferir
package.jsonscripts invocados desde CI
Convenciones CI/CD
- Reutilizar cache de dependencias (Node, etc.) ya configurada en el repo
- Stages: lint → test → build → deploy (omitir solo si el repo no tiene toolchain)
- Security checks en pipeline cuando existan (audit, SAST) — no inventar pipeline paralelo
Deploy (Firebase default)
- Reutilizar
firebase.jsontargets y--onlyexistentes - Predeploy hooks compartidos para lint/test/build
- Coordinar con arquitecto qué recursos se despliegan
Estrategias de deploy
Elegir según contexto del repo (documentar en entrega):
- Rolling — default razonable para Hosting/Functions
- Blue/green o canary — solo si el repo ya tiene patrón o hay requisito explícito
Rollback
- Enlazar runbooks en
docs/06_operations/si existen - No documentar rollback ad hoc sin revisar procedimiento existente (skill
devops/references/rollback-runbook.md)
Referencias
- Skill táctica:
.cursor/skills/devops/SKILL.md - Stack web:
docs/03_reference/web-stack-default.md(DOC-REF-005)
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.
- 4d ago First seen · 46 lines · 0 tokens per session scan A d4c8012be013
40-devops is a cursor rule 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 462 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 cursor rules, from other repositories
platform-engineer
Cursor rule "platform-engineer" from ulises-jeremias/agent-toolkit, covering platform engineer, responsibility, main skill domains, when invoked and delegate to skills.
atmos-rules
This is a Golang CLI project using Cobra for command structure and Viper for configuration management. The project maintains high code quality standards through golangci-lint and aims for maximum test coverage. The repository also includes the website source code for https://atmos.tools.
kubernetes
Kubernetes and OpenShift workload generation rules — security defaults, resource limits, probes.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.