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 Plazmodium/odin-workflow --skill test-driven-developmentgit clone --depth 1 https://github.com/Plazmodium/odin-workflowWrote 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/plazmodium/odin-workflow/test-driven-development)<a href="https://agentmods.dev/skills/plazmodium/odin-workflow/test-driven-development"><img src="https://agentmods.dev/badge/skills/plazmodium/odin-workflow/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/plazmodium/odin-workflow/test-driven-development"><img src="https://agentmods.dev/badge/skills/plazmodium/odin-workflow/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.00025 | $0.00341 |
| Opus 5.5 | $0.00010 | $0.00136 |
| Sonnet 5.5 | $0.00005 | $0.00068 |
| Haiku 4.5 | $0.00003 | $0.00034 |
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
test-driven-development
When To Use
- Implementing behavior, fixing bugs, or changing logic.
- A regression needs to stay fixed.
- Existing tests do not cover the acceptance criteria.
Workflow
- Identify the behavior that must be proven.
- Write the smallest failing test first when practical.
- Run it and confirm it fails for the expected reason.
- Write the minimum code needed to pass.
- Run the focused test and then the smallest relevant broader check.
- Refactor only with tests green.
- Prefer the test pyramid: mostly unit, some integration, few end-to-end.
- Keep tests DAMP: readable as specifications, even with some duplication.
Anti-Rationalization
| Excuse | Rebuttal |
|---|---|
| "I'll write tests later." | Later is where tests disappear. Write the proving test now. |
| "This is just plumbing." | Infrastructure changes can break behavior and need proof. |
| "Mocks are enough." | Mock-heavy tests can prove implementation details, not behavior. |
| "The UI looked fine once." | Manual observation is useful evidence, not a replacement for durable tests. |
Verification
- The test fails before the fix when feasible.
- The test passes after the fix.
- The test asserts user-visible or domain behavior, not incidental structure.
Exit Criteria
- Correct behavior is protected by an appropriate test or a clearly justified verification alternative.
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 · 45 lines · 25 tokens per session scan A 3738f577ab65
test-driven-development is a skill published in the GitHub repository Plazmodium/odin-workflow (0 stars, last pushed 5mo ago), licensed MIT. It adds 25 tokens to every session and 341 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-09-03.
Other skills, from other repositories
orch-tdd
Use when implementing a feature via test-driven development - write a failing test first, get to green with the smallest correct change, then refactor. Enforces vertical slice shape and red-commit-hash evidence.
aep-framework
Agile Engineering Process (Align-Execute-Prove) methodology with phase planning, test matrices, and evaluation harnesses.
testing
TDD/BDD testing principles. Use when writing tests, reviewing test coverage, setting up testing, or discussing test strategy and test architecture.
agent-test-generator
Specialist subagent: Generates comprehensive test suites using TDD patterns. Use only when the user explicitly asks for tests, improved coverage, or test-first development.
refactor-ops
Safe refactoring patterns - extract, rename, restructure with test-driven methodology and dead code detection. Use for: refactor, refactoring, extract function, extract component, rename, move file, restructure, dead code, unused imports, code smell, duplicate code, long function, god object, feature envy, DRY…
pair-programming
AI-assisted pair programming with multiple modes (driver/navigator/switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Features automatic role switching, continuous code review, security scanning, and performance optimization with…