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/zeikar/hyperclaude/hyper-tddnpx skills add zeikar/hyperclaude --skill hyper-tddgit clone --depth 1 https://github.com/zeikar/hyperclaudeWhat 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.00058 | $0.00397 |
| Opus 5 | $0.00029 | $0.00198 |
| Sonnet 5 | $0.00012 | $0.00079 |
| Haiku 4.5 | $0.00006 | $0.00040 |
Grade A, and why
hyper-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 2d 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.
What it actually says
hyper-tdd
Test-driven discipline tailored to this author's preferences.
The loop
- Write the failing test first. Name the behavior, not the implementation. The test should compile/import but fail because the behavior doesn't exist yet.
- Run it. Confirm it fails for the right reason. "Cannot find function" is fine. "ReferenceError because of typo in test" is not — fix the test.
- Write the minimum code to make it pass. Resist scope creep. No "while I'm here" edits.
- Run it. Confirm it passes.
- Commit. One behavior, one commit. Commit messages describe the behavior, not the code.
- Refactor if there's a clear smell. Tests must still pass after.
Skip TDD when
- Touching only documentation, comments, or formatting.
- Renaming a symbol (an LSP/grep operation, not a behavior change).
- One-shot migration scripts that run once and get deleted.
- Config-only changes (e.g., updating a
.gitignore).
What "minimum" means here
Implement only what the current test requires. If you need a helper, add the simplest version. Do not pre-build for tests you might write later — write that test first, then the helper.
What good test names look like
- ✅
slugify drops non-ASCII characters - ✅
cli --dry-run prints JSON without spawning codex - ❌
test_slugify(says nothing) - ❌
slugify works correctly(vague)
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.
- 2d ago First seen · 36 lines · 58 tokens per session scan A c653dbdc4692
hyper-tdd is a skill published in the GitHub repository zeikar/hyperclaude (3 stars, last pushed 15d ago), licensed MIT. It adds 58 tokens to every session and 397 once invoked, about $0.0003 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
tdd-guide
Comprehensive Test Driven Development guide for engineering subagents with multi-framework support, coverage analysis, and intelligent test generation.
Delphi Test-Driven Development (TDD) and DUnitX
Guidelines on how the AI should act and code when the user requests TDD, unit tests, DUnitX or fakes/mocks using Interfaces in Delphi.
abd-test
ABD Testing agent: auto-detects the test framework, writes tests matching project style, runs the suite, and records a test artifact.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code. Red-Green-Refactor cycle ensures tests pass.
tdd
Test-Driven Development (TDD) skill for Red-Green-Refactor cycle. Use when implementing features with tests first, minimal code to pass, then refactor. Teammates execute TDD autonomously within their own context in Agent Teams.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.