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/VersoXBT/claude-initial-setupWrote 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/agents/versoxbt/claude-initial-setup/tdd-guide)<a href="https://agentmods.dev/agents/versoxbt/claude-initial-setup/tdd-guide"><img src="https://agentmods.dev/badge/agents/versoxbt/claude-initial-setup/tdd-guide/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/agents/versoxbt/claude-initial-setup/tdd-guide"><img src="https://agentmods.dev/badge/agents/versoxbt/claude-initial-setup/tdd-guide.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.00096 | $0.00817 |
| Opus 5.5 | $0.00038 | $0.00327 |
| Sonnet 5.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 1mo 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.
- 1mo 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 5mo ago), licensed MIT. It adds 96 tokens to every session and 817 once invoked, about $0.0004 per session on Opus 5.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
backend-development-tdd-orchestrator
Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.
prd-testability-judge
Evaluates PRD acceptance criteria testability and language precision.
walkthrough-analyzer
Use this agent after cycle completion for cycles with UI stories, or when the user requests interactive usability testing. Acts like a real first-time user - clicks every button, checks every state transition, and reports what doesn't feel right. Browser-only - never reads source code. Context: Cycle with UI stories…
qa-analyzer
Use this agent after cycle completion or when the user requests bug hunting and QA analysis. World-class QA analyst that finds bugs before users do — thinks like a confused user, power user, and malicious attacker. Documents each issue precisely so it can be filed as a bug. Context: User just completed a cycle and…
tester
Use this agent after chunk implementation to create comprehensive test suites, or when the user requests test generation. Creates unit, integration, and edge case tests to ensure code works correctly and provide shipping confidence. Context: All chunks are implemented, orchestrator invokes testing phase. user: "All…
mb-rules-enforcer
Engineering-rules enforcer — runs deterministic SRP / Clean Architecture / TDD-delta checks against changed files and returns a structured JSON report. Invoked by /review, /commit, /pr, and plan-verifier Step 3.6.