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 skills/romiluz13/cc-teams/test-driven-developmentnpx skills add romiluz13/cc-teams --skill test-driven-developmentgit clone --depth 1 https://github.com/romiluz13/cc-teamsWhat 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 | $0.00018 | $0.03758 |
| Opus 5 | $0.00009 | $0.01879 |
| Sonnet 5 | $0.00004 | $0.00752 |
| Haiku 4.5 | $0.00002 | $0.00376 |
Grade A, and why
test-driven-development 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 — 541 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test-Driven Development (TDD)
Overview
Write the test first. Watch it fail. Write minimal code to pass.
Core principle: If you didn't watch the test fail, you don't know if it tests the right thing.
Task completion is not goal achievement. Passing a task requires proof, not intent.
No proof, no PASS. No fresh evidence, no completion claim.
Violating the letter of the rules is violating the spirit of the rules.
Test Process Discipline (CRITICAL)
Problem: Test runners (Vitest, Jest) default to watch mode, leaving processes hanging indefinitely. 61 hanging processes = frozen computer.
Mandatory Rules:
- Always use run mode - Never invoke watch mode:
- Vitest:
npx vitest run(NOTnpx vitest) - Jest:
CI=true npx jestornpx jest --watchAll=false - npm scripts:
CI=true npm testornpm test -- --run
- Vitest:
- Prefer CI=true prefix for all test commands:
CI=true npm test - Timeout guard: If CI handling is uncertain, prefix with
timeout 60sso the Bash tool never hangs indefinitely:timeout 60s npx vitest run - After TDD cycle complete, verify no orphaned processes:
pgrep -f "vitest|jest" || echo "Clean" - Kill if found:
pkill -f "vitest|jest" 2>/dev/null || true - IDE vs CLI truth: If CLI tests/builds pass with exit 0, trust the CLI over stale IDE/LSP diagnostics during active generation.
Phase Execution Guard
If you are working from a plan, treat the current approved phase as the contract.
Recover and follow:
objectiveinputsfiles/surfacesexpected artifactsrequired checkscheckpoint typeexit criteria
If a non-trivial phase is missing these and the work would become guesswork, stop and ask the lead for a clarified phase instead of inventing one.
When to Use
Always:
- New features
- Bug fixes
- Refactoring
- Behavior changes
Exceptions (ask your human partner):
- Throwaway prototypes
- Generated code
- Configuration files
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 · 541 lines · 18 tokens per session scan A 547c8b00f6a6
test-driven-development is a skill published in the GitHub repository romiluz13/cc-teams (5 stars, last pushed 4mo ago), licensed MIT. It adds 18 tokens to every session and 3,758 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-08-31.
Other skills, from other repositories
agent-integration
Run all three agent integration phases sequentially: research, write-tests, and implement using E2E-first TDD (unit tests written last). For individual phases, use /agent-integration:research, /agent-integration:write-tests, or /agent-integration:implement. Use when the user says "integrate agent", "add agent…
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
code-assist
Guides implementation of code tasks using test-driven development in an Explore, Plan, Code, Commit workflow. Acts as a Technical Implementation Partner and TDD Coach — following existing patterns, avoiding over-engineering, and producing idiomatic, modern code.
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
css-design-tdd
Test-driven CSS design system modifications. Run checks before/after CSS changes to verify token usage, variable definitions, fallbacks, and consistency. Use when modifying CSS tokens, fixing design inconsistencies, or auditing CSS architecture.
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.