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/30-testing)<a href="https://agentmods.dev/rules/mazalucas/el-dt-lightweight-army/30-testing"><img src="https://agentmods.dev/badge/rules/mazalucas/el-dt-lightweight-army/30-testing/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/rules/mazalucas/el-dt-lightweight-army/30-testing"><img src="https://agentmods.dev/badge/rules/mazalucas/el-dt-lightweight-army/30-testing.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.00285 |
| Opus 5 | $0.00000 | $0.00143 |
| Sonnet 5 | $0.00000 | $0.00057 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
30-testing 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 5d 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
Testing
Tipos de tests
- Unit: Lógica aislada; mocks para dependencias
- Integration: Múltiples unidades; preferir tests reales sobre mocks cuando sea práctico
- E2E: Flujos críticos de usuario
Cobertura
- Priorizar código crítico (lógica de negocio, edge cases)
- No obsesionarse con 100%; calidad sobre cantidad
Mocks
- Mockear dependencias externas (APIs, DB)
- Evitar mocks excesivos que oculten bugs de integración
Estructura
- Un test file por módulo/componente
- Nombres descriptivos:
describe('FeatureX', () => { it('should do Y when Z', ...) })
Reutilización (reuse-first)
Regla transversal: 15-engineering-reuse · skill qa · DOC-REF-006.
- Fixtures y factories compartidos — no duplicar setup por archivo
- Un helper por concepto — extender mocks existentes
- Ejecutar suite del repo cuando exista toolchain (skill
qa/references/toolchain.md)
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.
- 5d ago First seen · 37 lines · 0 tokens per session scan A 4f1f35a83b54
30-testing 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 285 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
testing-strategy
Comprehensive testing approach for the Rakit UI AI design selection tool.
hatch3r-testing
Coverage thresholds, mocking strategy, property-based testing, mutation-score targets, flaky test quarantine, and snapshot test discipline.
go-test
Rules for writing and modifying test files (test.go) in go-crypto-wallet.
issues-tests
Backend test conventions — QuarkusTest, REST Assured, Given, ArchUnit.
do-runner
Use the following runners.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.