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 agentmods add skills/djscheuf/agentic-dev-ecosystem-template/tdd-workflownpx skills add djscheuf/agentic-dev-ecosystem-template --skill tdd-workflowgit clone --depth 1 https://github.com/djscheuf/agentic-dev-ecosystem-templateWrote 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/djscheuf/agentic-dev-ecosystem-template/tdd-workflow)<a href="https://agentmods.dev/skills/djscheuf/agentic-dev-ecosystem-template/tdd-workflow"><img src="https://agentmods.dev/badge/skills/djscheuf/agentic-dev-ecosystem-template/tdd-workflow.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 | $0.00042 | $0.01506 |
| Opus 5 | $0.00021 | $0.00753 |
| Sonnet 5 | $0.00008 | $0.00301 |
| Haiku 4.5 | $0.00004 | $0.00151 |
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 3d 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Workflow (Composite)
Purpose
Complete Test-Driven Development cycle for implementing a feature or fixing a bug.
Overview
This workflow orchestrates the four TDD phases in a continuous cycle until the feature is complete.
┌─────────────────────────────────────────────────────────────────┐
│ TDD CYCLE │
│ │
│ ┌──────────┐ ┌─────────┐ ┌──────────┐ ┌───────────┐ │
│ │ THINK │───▶│ RED │───▶│ GREEN │───▶│ REFACTOR │ │
│ │ │ │ │ │ │ │ │ │
│ │ Plan │ │ Write │ │ Make it │ │ Clean up │ │
│ │ Tests │ │ Failing │ │ Pass │ │ Code │ │
│ │ │ │ Test │ │ │ │ │ │
│ └──────────┘ └─────────┘ └──────────┘ └─────┬─────┘ │
│ ▲ │ │
│ │ │ │
│ │ More tests in plan? │ │
│ └───────────────YES─────────────────────────────┘ │
│ │ │
│ NO │
│ ▼ │
│ ┌─────────┐ │
│ │ DONE │ │
│ └─────────┘ │
└─────────────────────────────────────────────────────────────────┘
Workflow Chain
Phase 1: Think
Reference: reference/think.md
Duration: 10-20 minutes
Output: Prioritized test plan
Execute Think phase (see reference/think.md for full steps)
├── Understand requirement
├── Identify all test cases
├── Prioritize by importance
└── Output: Test plan document
Phase 2-4: Red-Green-Refactor Loop
Repeat for each test in the plan
What ships with it
4 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.
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.
- 3d ago First seen · 206 lines · 42 tokens per session scan A 85ab5c12341f
tdd-workflow is a skill published in the GitHub repository djscheuf/agentic-dev-ecosystem-template (12 stars, last pushed 3d ago), licensed MIT. It adds 42 tokens to every session and 1,506 once invoked, about $0.0002 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
agent-integration
Run all three agent integration phases sequentially: research, write-tests, and implement using E2E-first TDD (unit tests written last). For individual phases, use /agent-integration:research, /agent-integration:write-tests, or /agent-integration:implement. Use when the user says "integrate agent", "add agent…
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
test-generation
Use when the user asks for tests, mentions TDD, or when new code has been written and needs test coverage.
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
css-design-tdd
Test-driven CSS design system modifications. Run checks before/after CSS changes to verify token usage, variable definitions, fallbacks, and consistency. Use when modifying CSS tokens, fixing design inconsistencies, or auditing CSS architecture.
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.