TDD Guard is an automated tool for Claude Code that checks whether coding work follows test-driven development by blocking implementation when required tests are missing or the code exceeds current test needs. It is for developers who want an AI coding agent to write failing tests first, implement minimally, and refactor according to configured lint rules.
Borrowing it
Nothing to install: this file belongs to nizos/tdd-guard. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nizos/tdd-guard/main/CLAUDE.mdgit clone --depth 1 https://github.com/nizos/tdd-guardWrote 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/instructions/nizos/tdd-guard/claude-md)<a href="https://agentmods.dev/instructions/nizos/tdd-guard/claude-md"><img src="https://agentmods.dev/badge/instructions/nizos/tdd-guard/claude-md.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.01055 | $0.01055 |
| Opus 5 | $0.00528 | $0.00528 |
| Sonnet 5 | $0.00211 | $0.00211 |
| Haiku 4.5 | $0.00105 | $0.00105 |
Grade A, and why
tdd-guard CLAUDE.md 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 8d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Guard
Project Goal
TDD Guard is a Claude Code hook that enforces Test-Driven Development by intercepting file operations. When Claude Code attempts to edit or write files, TDD Guard:
- Captures: Intercepts Edit, MultiEdit, and Write operations
- Analyzes: Examines test results, file paths, and code changes
- Validates: Checks TDD compliance using an AI model
- Blocks: Prevents operations that skip tests or over-implement
- Guides: Explains violations and suggests corrections
This automated enforcement maintains code quality without cluttering prompts with TDD reminders.
Development Workflow
Commit Guidelines
- Atomic commits: Each commit represents one logical change with its tests
- Test and implementation together: Never separate tests from the code they test
- Explain why, not what: Commit messages should explain the reason for the change
- Conventional format: Use prefixes to categorize changes: feat, fix, refactor, test, chore, docs
Example: feat: add network request filtering to reduce noise in captured data (explains why, not just what)
Project Structure
The codebase is organized with core functionality in src/ and language-specific reporters:
reporters/ # Language-specific test reporters
├── go/ # tdd-guard-go - Go test reporter
├── jest/ # tdd-guard-jest - Jest reporter (npm)
├── minitest/ # tdd-guard-minitest - Minitest reporter (gem)
├── phpunit/ # tdd-guard/phpunit - PHPUnit reporter (composer)
├── pytest/ # tdd-guard-pytest - Pytest reporter (pip)
├── rspec/ # tdd-guard-rspec - RSpec reporter (gem)
├── rust/ # tdd-guard-rust - Rust test reporter (crates.io)
├── storybook/ # tdd-guard-storybook - Storybook test-runner reporter (npm)
├── test/ # Shared test artifacts and integration tests
└── vitest/ # tdd-guard-vitest - Vitest reporter (npm)
src/ # Main CLI application
├── cli/ # Hook entry point and context builder
├── config/ # Configuration management
├── contracts/ # Types and Zod schemas
├── guard/ # Guard enable/disable management
├── hooks/ # Claude Code hook parsing and processing
├── linters/ # ESLint integration for code quality
├── processors/ # Test result and lint processing
├── providers/ # Model and linter client factories
├── storage/ # Storage abstractions
├── validation/ # TDD principle validation
│ ├── validator.ts # Sends context to AI model and parses response
│ ├── context/ # Formats operations for AI validation
│ ├── prompts/ # TDD validation rules and AI instructions
│ └── models/ # Claude SDK and Anthropic API clients
└── index.ts # Package entry point
test/ # Main test suite (hooks, integration, utils)
docs/ # Documentation (ADRs, configuration, etc.)
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.
- 8d ago First seen · 100 lines · 1,055 tokens per session scan A bfa9a6cdbe40
tdd-guard CLAUDE.md is an instructions file published in the GitHub repository nizos/tdd-guard (2,332 stars, last pushed 22d ago), licensed MIT. It adds 1,055 tokens to every session, about $0.0053 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-30.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.