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 commands/doncheli/don-cheli-sdd/teagit clone --depth 1 https://github.com/doncheli/don-cheli-sddWrote 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/doncheli/don-cheli-sdd/tea)<a href="https://agentmods.dev/commands/doncheli/don-cheli-sdd/tea"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/tea.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.00097 | $0.01766 |
| Opus 5 | $0.00048 | $0.00883 |
| Sonnet 5 | $0.00019 | $0.00353 |
| Haiku 4.5 | $0.00010 | $0.00177 |
Grade A, and why
tea 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dc:tea
Objetivo
Módulo de Testing Autónomo End-to-End (TEA): genera archivos de test, los ejecuta y produce un reporte de resultados y cobertura. Integra con el pipeline TDD del framework, se ejecuta tras /dc:implementar y auto-detecta el framework de testing del proyecto.
Uso
/dc:tea # Ejecutar ciclo completo
/dc:tea @specs/features/pagos/ # Solo dominio específico
/dc:tea --fase analizar # Solo fase 1
/dc:tea --fase generar # Solo fase 2
/dc:tea --fase ejecutar # Solo fase 3
/dc:tea --tipo unit # Solo tests unitarios
/dc:tea --tipo integration # Solo tests de integración
/dc:tea --tipo contract # Solo tests de contrato
/dc:tea --seco # Mostrar plan sin ejecutar
Comportamiento — 4 Fases
Fase 1: Analizar
LEER spec Gherkin (.feature) del dominio objetivo
LEER código de implementación existente
IDENTIFICAR:
├── Funciones y métodos públicos sin tests
├── Escenarios Gherkin sin cobertura
├── Rutas de error no testeadas
└── Contratos de integración (si hay openapi.yaml o contrato-api.md)
DETECTAR framework de testing:
├── package.json → Jest / Vitest / Mocha
├── pyproject.toml / setup.cfg → Pytest / Unittest
├── go.mod → Go test
├── Gemfile → RSpec
└── pom.xml / build.gradle → JUnit
REPORTAR plan de generación antes de ejecutar
Fase 2: Generar
CREAR archivos de test según framework detectado
TIPOS soportados:
├── unit: un test por función pública, cubre happy path + errores
├── integration: flujos end-to-end desde HTTP hasta DB
└── contract: verificar que API cumple spec OpenAPI
CONVENCIONES de nombrado:
├── Jest/Vitest: *.test.ts, *.spec.ts
├── Pytest: test_*.py
├── Go: *_test.go
└── RSpec: *_spec.rb
PLANTILLA mínima por test:
├── Arrange: estado inicial (fixtures, mocks, factories)
├── Act: llamada al código bajo prueba
└── Assert: verificación del resultado esperado
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 · 191 lines · 0 tokens per session scan A eec1712e1c24
tea is a command published in the GitHub repository doncheli/don-cheli-sdd (57 stars, last pushed 26d ago), licensed Apache-2.0. It adds 97 tokens to every session and 1,766 once invoked, about $0.0005 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 commands, from other repositories
verify-work
Validate built features through conversational UAT.
e2e
Create and run E2E tests across web, mobile, and desktop with auto-detection and CLI-first toolchains.
add-phase
Add phase to end of current milestone in roadmap.
remove-phase
Remove a future phase from roadmap and renumber subsequent phases.
research-phase
Research how to implement a phase (standalone — usually use /pbr:plan-phase instead).
reapply-patches
Reapply local modifications after a PBR update.