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/rlajous/claude-code-commands/tddnpx skills add rlajous/claude-code-commands --skill tddgit clone --depth 1 https://github.com/rlajous/claude-code-commandsWrote 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/rlajous/claude-code-commands/tdd)<a href="https://agentmods.dev/skills/rlajous/claude-code-commands/tdd"><img src="https://agentmods.dev/badge/skills/rlajous/claude-code-commands/tdd.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.00020 | $0.02884 |
| Opus 5 | $0.00010 | $0.01442 |
| Sonnet 5 | $0.00004 | $0.00577 |
| Haiku 4.5 | $0.00002 | $0.00288 |
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 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 — 498 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross-runtime: follow runtime compatibility for invocation, delegation, configuration precedence, state paths, and permissions.
You are helping implement a ticket using Test-Driven Development (TDD). Your task is to guide the user through the RED-GREEN-REFACTOR cycle: write failing tests first, implement code to pass tests, then refactor while keeping tests green.
Step 1: Load Configuration
Check for configuration and context:
# Check for config and context files
if [ -f ".git-workflow/config.yaml" ]; then
CONFIG_PATH=".git-workflow/config.yaml"
elif [ -f ".claude/config.yaml" ]; then
CONFIG_PATH=".claude/config.yaml" # legacy read-only fallback
else
CONFIG_PATH=""
fi
if [ -f ".git-workflow/pr-context.json" ]; then
CONTEXT_PATH=".git-workflow/pr-context.json"
elif [ -f ".claude/.pr-context.json" ]; then
CONTEXT_PATH=".claude/.pr-context.json" # legacy read-only fallback
else
CONTEXT_PATH=""
fi
Load from the resolved CONFIG_PATH (if one exists):
qa:
tdd:
confirmBeforeGreen: true
confirmBeforeRefactor: true
maxRedAttempts: 3
runFullSuiteEachPhase: false
autoStartServer: false
testing:
unit: auto
lint: auto
typeCheck: auto
issueTracker:
type: auto
Default Values (when no config):
qa:
tdd:
confirmBeforeGreen: true
confirmBeforeRefactor: true
maxRedAttempts: 3
runFullSuiteEachPhase: false
autoStartServer: false
Step 2: Parse Arguments
Extract from $ARGUMENTS:
$ARGUMENTS
Patterns to Extract:
| Pattern | Example | Meaning |
|---|---|---|
| Ticket ID | PROJ-123, ENG-456 |
Issue tracker ticket |
| GitHub Issue | #789 |
GitHub issue number |
| Linear URL | https://linear.app/.../ENG-456/... |
Extract ticket ID |
| Jira URL | https://....atlassian.net/browse/PROJ-123 |
Extract ticket ID |
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 · 498 lines · 20 tokens per session scan A 2c2cd8de62f7
tdd is a skill published in the GitHub repository rlajous/claude-code-commands (30 stars, last pushed 4d ago), licensed MIT. It adds 20 tokens to every session and 2,884 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
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.