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 New1Direction/korgex --skill test-driven-developmentgit clone --depth 1 https://github.com/New1Direction/korgexWrote 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/new1direction/korgex/test-driven-development)<a href="https://agentmods.dev/skills/new1direction/korgex/test-driven-development"><img src="https://agentmods.dev/badge/skills/new1direction/korgex/test-driven-development/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/new1direction/korgex/test-driven-development"><img src="https://agentmods.dev/badge/skills/new1direction/korgex/test-driven-development.svg" alt="Reviewed on agentmods" width="80" 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.00021 | $0.00287 |
| Opus 5.5 | $0.00008 | $0.00115 |
| Sonnet 5.5 | $0.00004 | $0.00057 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
test-driven-development 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 1mo 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
Use this whenever you add or change behaviour. The discipline is what makes the test trustworthy — a test you never saw fail proves nothing.
- RED — write one failing test. Pick the smallest next behaviour. Write a test that asserts it, using real code (no mocks unless a dependency is truly unavailable). One behaviour per test; name it for the behaviour.
- Watch it fail. Run it. Confirm it fails for the right reason (the feature is missing), not a typo or import error. If it passes already, you're testing existing behaviour — fix the test.
- GREEN — minimal code. Write the least code that makes it pass. Don't add options, abstractions, or features the test doesn't demand.
- Watch it pass. Run it; confirm the whole suite stays green and the output is clean (no new warnings).
- REFACTOR. Improve names and remove duplication while green. Don't add behaviour here.
- Repeat for the next behaviour.
If a test is hard to write, the design is usually too coupled — simplify the interface before continuing.
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.
- 1mo ago First seen · 27 lines · 21 tokens per session scan A f7e5872e1d27
test-driven-development is a skill published in the GitHub repository New1Direction/korgex (5 stars, last pushed 7d ago), licensed MIT. It adds 21 tokens to every session and 287 once invoked, about $0.0001 per session on Opus 5.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
engineering-craft
Use when writing or changing any production code or tests — new features, bug fixes, refactors, or test authoring, in any language, by any model on any CLI.
vibe-test
A testing workflow that follows TDD, or test-driven development: write a test that fails, add the smallest code needed to pass it, then clean up the code. It produces tests and a test report.
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.
bad-case-to-dpo
A guide to turning failed production agent runs into training and evaluation data. It explains how to find the first mistake, create preference examples for DPO (Direct Preference Optimization), and check that a fix does not damage other tasks.
adk-go-self-review
Review an ADK Go change the way a maintainer will — a fresh-context pass over the whole diff, five lenses (correctness and tests, scope, simplicity, style, adk-python parity), and the mutation check that proves your tests pin the change. Use before opening a PR, before any later push that changes code, and when asked…
fable-judge
Adversarial verification of finished work. Treats any "done" as a set of claims, then re-runs the claimed verifications, diffs what actually changed, detects weakened tests and false completion claims, and delivers an evidence-based verdict (VERIFIED / VERIFIED WITH CAVEATS / REFUTED). Use after any agent or model…