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 skills add brain-bootstrap/claude-code-brain-bootstrap --skill tddgit clone --depth 1 https://github.com/brain-bootstrap/claude-code-brain-bootstrapWrote 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/skills/brain-bootstrap/claude-code-brain-bootstrap/tdd)<a href="https://agentmods.dev/skills/brain-bootstrap/claude-code-brain-bootstrap/tdd"><img src="https://agentmods.dev/badge/skills/brain-bootstrap/claude-code-brain-bootstrap/tdd/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/skills/brain-bootstrap/claude-code-brain-bootstrap/tdd"><img src="https://agentmods.dev/badge/skills/brain-bootstrap/claude-code-brain-bootstrap/tdd.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.00025 | $0.00673 |
| Opus 5.5 | $0.00010 | $0.00269 |
| Sonnet 5.5 | $0.00005 | $0.00135 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
tdd 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explore-Plan-Act TDD Workflow
When implementing any feature or bugfix, follow the Explore → Plan → Act discipline.
Process
1. EXPLORE — Investigate Before Coding
- Read the codebase first — use Grep, Read, and LS to understand the current state
- Trace the code path related to the change: entry points → dependencies → side effects
- Check
CLAUDE.mdand relevantclaude/*.mddocs for domain-specific patterns - Identify existing tests in the area — understand what's already covered
- Look for similar implementations elsewhere in the codebase to follow conventions
- Output: Clear understanding of what exists, what patterns to follow, what constraints apply
2. PLAN — Design the Solution + Write Failing Tests
- Design the solution approach based on what you explored
- Document any assumptions or open questions
- Write failing tests that describe the expected behavior BEFORE implementation
- Each test should be specific and focused on one behavior
- Run the tests and confirm they fail for the right reason
- Consider edge cases: null/undefined, empty arrays, concurrent calls, boundary values
- Output: Failing tests that serve as a specification for the implementation
3. ACT — Implement with TDD Cycle
- Write the simplest code that makes the tests pass
- Do not add code that isn't required by a failing test
- Run the tests and confirm they pass
- Refactor while keeping tests green — clean up, extract patterns, improve naming
- Run all tests to ensure nothing breaks
- Repeat for each component or behavior
- Output: Working implementation with green tests
Testing Conventions
Framework per Layer
- Unit: none (syntax-check)
- Integration: none (syntax-check)
What to Test
- Every new branch/case in switch statements
- Every guard condition
- Every new field (cross-layer: DTO → backend → frontend)
- Edge cases: null/undefined, empty arrays, concurrent calls
Code Style
- Follow project formatter rules
- Use descriptive test names:
it('should <behavior> when <condition>') - Follow existing test patterns in the service being modified
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 · 71 lines · 25 tokens per session scan A e2d8fb9ca818
tdd is a skill published in the GitHub repository brain-bootstrap/claude-code-brain-bootstrap (11 stars, last pushed 5mo ago), licensed MIT. It adds 25 tokens to every session and 673 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.
python
Python development with ruff, mypy, pytest - TDD and type safety.
tdd
This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the…