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 alirezarezvani/claude-code-skill-factory --skill tdd-guidegit clone --depth 1 https://github.com/alirezarezvani/claude-code-skill-factoryWrote 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/alirezarezvani/claude-code-skill-factory/tdd-guide)<a href="https://agentmods.dev/skills/alirezarezvani/claude-code-skill-factory/tdd-guide"><img src="https://agentmods.dev/badge/skills/alirezarezvani/claude-code-skill-factory/tdd-guide.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.00026 | $0.02494 |
| Opus 5 | $0.00013 | $0.01247 |
| Sonnet 5 | $0.00005 | $0.00499 |
| Haiku 4.5 | $0.00003 | $0.00249 |
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 7d 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 — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Guide - Test Driven Development for Engineering Teams
A comprehensive Test Driven Development skill that provides intelligent test generation, coverage analysis, framework integration, and TDD workflow guidance across multiple languages and testing frameworks.
Capabilities
Test Generation
- Generate Test Cases from Requirements: Convert user stories, API specs, and business requirements into executable test cases
- Create Test Stubs: Generate test function scaffolding with proper naming, imports, and setup/teardown
- Generate Test Fixtures: Create realistic test data, mocks, and fixtures for various scenarios
TDD Workflow Support
- Guide Red-Green-Refactor: Step-by-step guidance through TDD cycles with validation
- Suggest Missing Scenarios: Identify untested edge cases, error conditions, and boundary scenarios
- Review Test Quality: Analyze test isolation, assertions quality, naming conventions, and maintainability
Coverage & Metrics Analysis
- Calculate Coverage: Parse LCOV, JSON, and XML coverage reports for line/branch/function coverage
- Identify Untested Paths: Find code paths, branches, and error handlers without test coverage
- Recommend Improvements: Prioritized recommendations (P0/P1/P2) for coverage gaps and test quality
Framework Integration
- Multi-Framework Support: Jest, Pytest, JUnit, Vitest, Mocha, RSpec adapters
- Generate Boilerplate: Create test files with proper imports, describe blocks, and best practices
- Configure Test Runners: Set up test configuration, coverage tools, and CI integration
Comprehensive Metrics
- Test Coverage: Line, branch, function coverage with gap analysis
- Code Complexity: Cyclomatic complexity, cognitive complexity, testability scoring
- Test Quality: Assertions per test, isolation score, naming quality, test smell detection
- Test Data: Boundary value analysis, edge case identification, mock data generation
- Test Execution: Timing analysis, slow test detection, flakiness detection
- Missing Tests: Uncovered edge cases, error handling gaps, missing integration scenarios
What ships with it
14 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- coverage_analyzer.py 15 KB runs code
- expected_output.json 2.3 KB
- fixture_generator.py 14 KB runs code
- format_detector.py 12 KB runs code
- framework_adapter.py 14 KB runs code
- HOW_TO_USE.md 7.0 KB
- metrics_calculator.py 15 KB runs code
- output_formatter.py 12 KB runs code
- README.md 18 KB
- sample_coverage_report.lcov 615 B
- sample_input_python.json 1.4 KB
- sample_input_typescript.json 1.4 KB
- tdd_workflow.py 17 KB runs code
- test_generator.py 14 KB runs code
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.
- 7d ago First seen · 288 lines · 26 tokens per session scan A b18e46853f1b
tdd-guide is a skill published in the GitHub repository alirezarezvani/claude-code-skill-factory (858 stars, last pushed 9mo ago), licensed MIT. It adds 26 tokens to every session and 2,494 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-30.
Other skills, from other repositories
hyper-tdd
Use when about to write or modify behavior-bearing code — functions, business logic, bug fixes — before writing any production code. Also when the user invokes /hyperclaude:hyper-tdd. Forces a failing test first so you watch it fail for the right reason.
Delphi Test-Driven Development (TDD) and DUnitX
Guidelines on how the AI should act and code when the user requests TDD, unit tests, DUnitX or fakes/mocks using Interfaces in Delphi.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.
tdd-loop
Implement a known feature, behavior change, or diagnosed bug with a red-green-refactor loop. Use when the user asks to add, build, implement, or fix behavior and automated tests exist or should exist. For an unknown failure cause use debug-protocol first; for model, prompt, RAG, or agent quality use…
tdd
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.