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 slowdini/slow-powers --skill working-with-tddgit clone --depth 1 https://github.com/slowdini/slow-powersWrote 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/slowdini/slow-powers/working-with-tdd)<a href="https://agentmods.dev/skills/slowdini/slow-powers/working-with-tdd"><img src="https://agentmods.dev/badge/skills/slowdini/slow-powers/working-with-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.00020 | $0.01147 |
| Opus 5 | $0.00010 | $0.00574 |
| Sonnet 5 | $0.00004 | $0.00229 |
| Haiku 4.5 | $0.00002 | $0.00115 |
Grade A, and why
working-with-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 8d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test-driven development (TDD)
Write the test first. Watch it fail. Write minimal code to pass. Refactor.
THE IRON LAW: NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST.
Write production code before the test? Delete it. Start over. Do not keep it for "reference" or "adapt" it. Delete means delete.
Violating the letter of the rules is violating the spirit of the rules.
REQUIRED PREREQUISITE: You must have already completed
slow-powers:working-in-isolation— establish an isolated workspace before writing any test or production code.
REQUIRED NEXT SKILL: You must complete
slow-powers:verifying-development-worknext, after the TDD implementation work is done and before claiming the task is complete or handing work back to the user.
Red-green-refactor cycle
- RED — Write a failing test:
- Write one minimal, focused test showing what the behavior should do.
- Use real code and real inputs; avoid mocks unless absolutely unavoidable. Before committing a test, scan it against the Testing anti-patterns table below; if it matches a row, read the named section of the testing anti-patterns reference first.
- Verify RED — Watch it fail:
- Run the test command:
npm test/pytest/go test. - MANDATORY: Verify it fails for the expected reason (for example, a function is undefined or a value is incorrect), not because of a typo or build error.
- Run the test command:
- GREEN — Write minimal code:
- Write the simplest possible implementation to make the test pass.
- Avoid over-engineering or speculative optimization.
- Verify GREEN — Watch it pass:
- Run the test suite. Verify the test passes, and no regressions are introduced.
- REFACTOR — Clean up:
- Clean up names, remove duplication, and extract helper methods.
- Keep the test suite green. Do not add new behavior during refactoring.
Example: code vs. mock testing
Good (focuses on real behavior)
test('retries failed operations 3 times', async () => {
let attempts = 0;
const operation = async () => {
attempts++;
if (attempts < 3) throw new Error('fail');
return 'success';
};
const result = await retryOperation(operation);
expect(result).toBe('success');
expect(attempts).toBe(3);
});
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.
- evals/baseline/BASELINE.md 988 B
- evals/baseline/benchmark.json 1.1 KB
- evals/baseline/NOTES.md 6.3 KB
- evals/evals.json 16 KB
- evals/fixtures/helper-tautology/formatMoney.ts 348 B runs code
- evals/fixtures/helper-tautology/package.json 61 B
- evals/fixtures/helper-tautology/test-utils.ts 316 B runs code
- evals/fixtures/paginated-fetch/package.json 60 B
- evals/fixtures/paginated-fetch/userList.ts 1.1 KB runs code
- evals/fixtures/render-user-card/package.json 61 B
- evals/fixtures/render-user-card/userCard.ts 458 B runs code
- evals/fixtures/slugify/package.json 52 B
- evals/fixtures/slugify/utils.ts 252 B runs code
- references/testing-anti-patterns.md 9.8 KB
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.
- 8d ago First seen · 113 lines · 20 tokens per session scan A c770ff51b108
working-with-tdd is a skill published in the GitHub repository slowdini/slow-powers (2 stars, last pushed 24d ago), licensed MIT. It adds 20 tokens to every session and 1,147 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-31.
Other skills, from other repositories
init-pipeline
Infrastructure skill for scaffolding pipeline enforcement into a project. Sets up Claude Code hooks (TDD classification gate, git guardrails, optional quality gate), pre-commit hooks (detects existing tools, defaults to Lefthook + Biome + pnpm if none found). Run when setting up a project for pipeline work, and again…
triage-issue
Invoked helper skill for deep bug diagnosis, usually delegated from /qa when a reported issue needs root-cause analysis and a TDD fix plan before implementation. Use when the cause is unclear, the bug is a regression, or the user explicitly wants diagnosis. Not for lightweight QA intake (use /qa) or already-clear…
tdd
Invoked helper skill for strict red-green-refactor implementation, usually delegated from /execute or bug-fix work shaped by /triage-issue. Use when backend behavior or behavior-heavy frontend logic should be built test-first through public interfaces. Not for shaping, decomposition, vague implementation tasks, or…
tdd
Enforces red-green-refactor TDD cycle with atomic commits per phase. Used when implementing features, fixing bugs, or when tests should drive the design.
specmint-tdd
TDD-first spec management for AI coding workflows. Use this skill when the user explicitly mentions specs, forging, or structured planning: says "forge", "forge a spec", "write a spec for X", "create a spec", "plan X as a spec", "resume", "what was I working on", "spec list/status/pause/switch/activate", "implement…
setup
Set up or update TDD Guard for the current project. Detects the test framework, installs or updates the matching reporter, and configures or migrates its configuration to match the current specification.