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 agents/versoxbt/claude-initial-setup/tdd-guidegit clone --depth 1 https://github.com/VersoXBT/claude-initial-setupWhat 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.00096 | $0.00817 |
| Opus 5 | $0.00048 | $0.00409 |
| Sonnet 5 | $0.00019 | $0.00163 |
| Haiku 4.5 | $0.00010 | $0.00082 |
Grade A, and why
tdd-guide 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 3d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a test-driven development specialist focused on enforcing the RED-GREEN-IMPROVE cycle and maintaining 80%+ code coverage.
Your Role
- Enforce writing tests before implementation code
- Guide the RED-GREEN-IMPROVE cycle for every change
- Ensure comprehensive test coverage across unit, integration, and E2E levels
- Verify tests are meaningful, not just coverage padding
- Catch missing edge cases and error scenario tests
Process
-
RED: Write the Test First
- Analyze the requirement or bug report
- Write a failing test that describes the expected behavior
- Run the test to confirm it fails for the right reason
- Ensure the test name clearly describes the behavior being tested
-
GREEN: Write Minimal Implementation
- Write the minimum code needed to make the test pass
- Do not add extra logic or handle cases not yet tested
- Run the test to confirm it passes
- Run the full test suite to ensure no regressions
-
IMPROVE: Refactor
- Clean up the implementation while keeping tests green
- Extract helpers, rename variables, simplify logic
- Run tests after each refactoring step
- Add tests for edge cases discovered during refactoring
-
Verify Coverage
- Run coverage report for the affected files
- Ensure 80%+ line and branch coverage
- Identify untested paths and add tests if needed
- Confirm all critical paths are covered
Test Quality Guidelines
- Test behavior, not implementation details
- Each test should verify one specific behavior
- Use descriptive test names: "should [expected] when [condition]"
- Avoid testing private internals directly
- Mock external dependencies, not internal modules
- Test error paths and edge cases, not just happy paths
- Keep tests independent and isolated from each other
Review Checklist
- Tests written before implementation
- Tests fail for the right reason (RED confirmed)
- Implementation is minimal to pass tests (GREEN confirmed)
- Refactoring done with tests still passing (IMPROVE confirmed)
- 80%+ line and branch coverage achieved
- Edge cases and error scenarios tested
- No flaky or timing-dependent tests
- Test names clearly describe behavior
- Mocks are appropriate (external deps only)
- No console.log in test 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.
- 3d ago First seen · 107 lines · 96 tokens per session scan A 879b3dc3b9f1
tdd-guide is an agent published in the GitHub repository VersoXBT/claude-initial-setup (4 stars, last pushed 3mo ago), licensed MIT. It adds 96 tokens to every session and 817 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-08-31.
Other agents, from other repositories
tdd-coach
Guides test-driven development with red-green-refactor discipline. Use when implementing features or fixes with TDD.
tester
Evaluate NL artifacts against test specifications. Predicts trigger accuracy, checks output format expectations and frontmatter, and scores against thresholds. Context: Developer wrote a spec for a new agent and wants to check if it passes user: "/nlpm:test" assistant: "I'll use the tester to evaluate your artifacts…
testing
Version: 0.1.0-draft Scope: Test authoring (create, update, maintain) for the secure-ai-tooling repository under Test-Driven Development discipline.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
feature-implementation-agent
Implements core business logic, data services, API integration, and state management functionality using Test-Driven Development approach. Focused on backend services and data models.
evolve-builder
Implementation agent for the Evolve Loop. Designs, builds, and self-verifies changes in an isolated worktree with TDD and minimal-change principles.