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 agentmods add rules/mazalucas/el-dt-lightweight-army/08-stack-web-defaultgit 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/08-stack-web-default)<a href="https://agentmods.dev/rules/mazalucas/el-dt-lightweight-army/08-stack-web-default"><img src="https://agentmods.dev/badge/rules/mazalucas/el-dt-lightweight-army/08-stack-web-default.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.00027 | $0.00876 |
| Opus 5 | $0.00014 | $0.00438 |
| Sonnet 5 | $0.00005 | $0.00175 |
| Haiku 4.5 | $0.00003 | $0.00088 |
Grade A, and why
08-stack-web-default 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 2d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stack web canónico (Firebase + Node)
Fuente de datos: vitals/data/engineering/web-stack.yaml. Override local opcional: .agents/engineering-stack.md.
Cuándo aplica
Activar esta regla cuando el pedido implique desarrollo web o arquitectura de producto web:
- App web, SPA, dashboard, admin panel
- Landing con backend o autenticación
- API REST/HTTP para cliente web o mobile
- MVP, PRD o SRD con componente técnico web
- Deploy, auth, base de datos o hosting para producto web
No aplica como stack DB/backend cuando: solo diseño Atelier sin implementación; video Remotion; tareas puramente de docs/marketing sin código.
Precedencia (soft default)
Resolver en este orden (mayor prioridad primero):
- Opt-out explícito del usuario — respeta la elección; documenta trade-offs si difiere del default.
- Stack del repo existente — inspeccionar señales antes de proponer migración:
firebase.json,firestore.rules,firestore.indexes.jsonpackage.json(dependenciasfirebase,vite,react)requirements.txt,go.mod,Cargo.toml,docker-composecon Postgres/MySQL- README o docs de arquitectura del proyecto
.agents/engineering-stack.md— si existe, usar como stack confirmado del proyecto.- Default DT —
web-stack.yaml: Node + Firebase completo; frontend Vite + React.
Si el repo ya tiene stack claro distinto (p. ej. Python/Django + Postgres), respetarlo. Mencionar el default DT solo como nota, no empujar migración.
Stack default (proyecto nuevo o ambiguo)
| Capa | Default |
|---|---|
| Runtime | Node.js LTS |
| Auth | Firebase Auth |
| Base de datos | Firestore |
| Backend/API | Cloud Functions for Firebase (Node) |
| Hosting | Firebase Hosting / App Hosting |
| Archivos | Cloud Storage |
| Secrets | Firebase Secrets |
| Frontend | Vite + React (Firebase JS SDK modular v9+) |
Alternativas (Supabase, Postgres, Python, etc.): solo proponer con trade-offs explícitos y después de opt-out del usuario o cuando el repo ya las usa.
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.
- 2d ago First seen · 89 lines · 27 tokens per session scan A f2ffaa192c14
08-stack-web-default is a cursor rule published in the GitHub repository Mazalucas/El-DT-Lightweight-Army (4 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 876 once invoked, about $0.0001 per session on Opus 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-09-03.
Other cursor rules, from other repositories
kubernetes
Kubernetes and OpenShift workload generation rules — security defaults, resource limits, probes.
platform-engineer
Cursor rule "platform-engineer" from ulises-jeremias/agent-toolkit, covering platform engineer, responsibility, main skill domains, when invoked and delegate to skills.
kubernetes
This rule provides comprehensive best practices for developing and maintaining Kubernetes applications and infrastructure, covering coding standards, security, performance, testing, and deployment.
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.