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 Claude-Code-Community-Ireland/claude-code-resources --skill tdd-workflowgit clone --depth 1 https://github.com/Claude-Code-Community-Ireland/claude-code-resourcesWrote 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/claude-code-community-ireland/claude-code-resources/tdd-workflow)<a href="https://agentmods.dev/skills/claude-code-community-ireland/claude-code-resources/tdd-workflow"><img src="https://agentmods.dev/badge/skills/claude-code-community-ireland/claude-code-resources/tdd-workflow/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/claude-code-community-ireland/claude-code-resources/tdd-workflow"><img src="https://agentmods.dev/badge/skills/claude-code-community-ireland/claude-code-resources/tdd-workflow.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.00050 | $0.02173 |
| Opus 5.5 | $0.00020 | $0.00869 |
| Sonnet 5.5 | $0.00010 | $0.00435 |
| Haiku 4.5 | $0.00005 | $0.00217 |
Grade A, and why
tdd-workflow 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test-Driven Development Workflow
Core Philosophy
TDD is a design discipline, not just a testing technique. Writing tests first forces you to think about the interface before the implementation, producing code that is inherently testable, loosely coupled, and driven by actual requirements.
The Red-Green-Refactor Loop
Step 1: RED — Write a Failing Test
- Identify the smallest piece of behavior to implement next.
- Write a test that describes that behavior from the caller's perspective.
- Run the test suite. The new test MUST fail.
- If the test passes without writing new code, either the behavior already exists or the test is wrong.
Checklist before moving to GREEN:
- The test describes WHAT, not HOW.
- The test name reads like a specification (e.g.,
it should return 404 when resource not found). - The test fails for the right reason (expected assertion failure, not a syntax error or import error).
- The test is isolated — it does not depend on other tests or external state.
Step 2: GREEN — Write the Minimal Implementation
- Write the simplest code that makes the failing test pass.
- It is acceptable — even encouraged — to hardcode values, use naive algorithms, or write "ugly" code at this stage.
- Do NOT add logic that is not required by a failing test.
- Run the full test suite. ALL tests must pass.
The "simplest thing that could work" principle:
- If one test expects
return 42, writereturn 42. Do not write a general formula yet. - If two tests expect different outputs, write an
ifstatement. Do not write a loop yet. - If three tests show a pattern, NOW consider a general algorithm.
Checklist before moving to REFACTOR:
- The new test passes.
- All previously passing tests still pass.
- No code was added beyond what the tests demand.
Step 3: REFACTOR — Improve the Design
- Look for duplication in both production code and test code.
- Extract methods, rename variables, simplify conditionals.
- Apply design patterns only when the code asks for them (three or more instances).
- Run the full test suite after every change. All tests must stay green.
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 · 262 lines · 50 tokens per session scan A 8a444cee8aa6
tdd-workflow is a skill published in the GitHub repository Claude-Code-Community-Ireland/claude-code-resources (11 stars, last pushed 4mo ago), licensed MIT. It adds 50 tokens to every session and 2,173 once invoked, about $0.0002 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…