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 klimentij/klimkit --skill klimkit-tddgit clone --depth 1 https://github.com/klimentij/klimkitWrote 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/klimentij/klimkit/klimkit-tdd)<a href="https://agentmods.dev/skills/klimentij/klimkit/klimkit-tdd"><img src="https://agentmods.dev/badge/skills/klimentij/klimkit/klimkit-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.00050 | $0.00374 |
| Opus 5 | $0.00025 | $0.00187 |
| Sonnet 5 | $0.00010 | $0.00075 |
| Haiku 4.5 | $0.00005 | $0.00037 |
Grade A, and why
klimkit-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 7d 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
Klimkit TDD
Use TDD to protect intent, not to create mechanical coverage. Keep each loop small enough that a failing test names the behavior being changed.
Workflow
- Ensure Klimkit's docs-first context exists. If the repo lacks the
docs/work/layout, useklimkit-setupfirst. - Read the request, acceptance checklist, existing tests, and nearby implementation before writing a test.
- Choose one vertical behavior slice. Avoid broad refactors before the first red test.
- Write or update the smallest test that should fail for the requested behavior.
- Run the focused test and confirm it fails for the expected reason.
- Implement the smallest robust change that makes the test pass.
- Run the focused test again.
- Refactor only the code touched by this slice, preserving green tests.
- Repeat for the next slice until the checklist is complete.
- Run broader checks that match the blast radius.
- Record the red/green evidence, final checks, skipped checks, and residual risk as a numbered note in the current
docs/work/phase folder.
Test Quality
- Test business behavior or safety properties, not implementation trivia.
- Prefer existing test frameworks, fixtures, factories, and naming conventions.
- Add integration or UI tests only when unit tests cannot catch the failure mode.
- If no suitable test harness exists, document the gap and provide a manual proof that directly exercises the behavior.
Use klimkit-diagnose first when the expected behavior is still unclear.
What ships with it
1 file 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.
- 7d ago First seen · 32 lines · 50 tokens per session scan A 7c5b4dc57670
klimkit-tdd is a skill published in the GitHub repository klimentij/klimkit (7 stars, last pushed 28d ago), licensed MIT. It adds 50 tokens to every session and 374 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
A Test-Driven Development guide. TDD means writing a failing test first, adding the smallest implementation that passes it, and then improving the code while keeping the tests passing.
debugging
A structured method for finding and fixing software bugs. It starts by writing a test that reproduces the failure, then investigates its underlying cause before making a small fix.
armada-tdd
Test-driven development for armada workers. Use before writing any implementation. Triggers on: TDD, failing test, test first, write a test.
fix-bug
Fixes a bug through test-driven debugging, reproduces it with a failing test, locates the root cause with evidence (file:line), then applies the smallest fix that resolves it without refactoring unrelated code. Use when the user wants to fix a bug, debug an issue, resolve an error, or investigate a failing test. Not…
forward-derivation
Derive BDD scenarios and TDD test skeletons from approved SDD specifications. ATDD acceptance test tables are optional output for specialized needs. Use when: spec is approved, starting BDD/TDD implementation, generating test structures. Keywords: forward derivation, spec to test, BDD generation, TDD skeleton, test…
bdd-assistant
A guide to Behavior-Driven Development, or BDD, a way to describe software behavior with examples in plain language before building it. It uses Given-When-Then scenarios and Gherkin, a structured format for those examples.