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.
git clone --depth 1 https://github.com/kumaran-is/claude-code-onboardingWrote 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/commands/kumaran-is/claude-code-onboarding/tdd)<a href="https://agentmods.dev/commands/kumaran-is/claude-code-onboarding/tdd"><img src="https://agentmods.dev/badge/commands/kumaran-is/claude-code-onboarding/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.1 | $0.00000 | $0.00688 |
| Opus 5 | $0.00000 | $0.00344 |
| Sonnet 5 | $0.00000 | $0.00138 |
| Haiku 4.5 | $0.00000 | $0.00069 |
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 4d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/tdd — Test-Driven Development Mode
Invokes the tdd-guide agent to enforce Red-Green-Refactor methodology on the current task.
When to Use
- Implementing a new feature: write tests first
- Adding a bug fix: write a reproducing test first, then fix
- Reviewing test quality: check coverage + edge case completeness
Behavior
When /tdd is invoked, the tdd-guide agent:
- Identifies the feature/behavior to be tested
- Writes the failing test (RED) — the test must fail before any implementation
- Writes minimum implementation (GREEN) — just enough to pass
- Refactors (REFACTOR) — clean up without changing behavior
- Verifies coverage — runs coverage report, flags gaps
DO / DON'T
| DO | DON'T |
|---|---|
| Write test before implementation | Write implementation then retrofit tests |
| Test behavior, not implementation | Test private methods or internal state |
| Use real stack test runner (JUnit5/pytest/Vitest/flutter_test) | Mock everything including the thing being tested |
| Cover all 8 edge case categories | Only test the happy path |
| Run tests 3x to confirm no flakiness | Ship after a single green run |
Coverage Requirements
- Minimum: 80% line coverage
- Critical code (auth, crypto, payments, data migrations): 100%
- Files below threshold are listed and must be addressed before marking feature done
Error Cases
| Situation | Response |
|---|---|
Test runner binary not found (mvnw, flutter, pytest, npm) |
Report "BUILD TOOL NOT FOUND — install [tool] or run from project root" |
| Test passes immediately without implementation (RED phase fails) | "⚠️ Test did not fail first — diagnose before proceeding. The behavior may already exist or the test assertion is wrong." |
| Refactor-only task (no new behavior) | Skip RED phase — run existing tests before and after. No new tests required. |
| Config/rename change | Run existing tests only — no new tests required per first-principles.md |
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.
- 4d ago First seen · 71 lines · 0 tokens per session scan A 060792dd2273
tdd is a command published in the GitHub repository kumaran-is/claude-code-onboarding (35 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 688 tokens. 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 commands, from other repositories
bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
usage-add
PitWay: Accumulate measured planning or qa token usage onto a milestone.
dashboard
Generar dashboard HTML local con métricas de eficiencia del proyecto SDD.
hub-tdd
TDD workflow for MCP Hub implementation. Types → Tests (red) → Implementation (green) with git gates.
eval
Evaluate and improve one healthcare agent's system prompt. Run up to 5 iterations of: prepare fixed questions -> answer -> judge -> improve -> re-score -> commit if better.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.