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/kbwen/agentic-os/test-driven-developmentnpx skills add KbWen/agentic-os --skill test-driven-developmentgit clone --depth 1 https://github.com/KbWen/agentic-osWhat 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.00023 | $0.00207 |
| Opus 5 | $0.00012 | $0.00103 |
| Sonnet 5 | $0.00005 | $0.00041 |
| Haiku 4.5 | $0.00002 | $0.00021 |
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- test-driven-development — 100% identical, 0 lines differ
What it actually says
Test-Driven Development
Overview
TDD uses the Red → Green → Refactor micro-cycle. First, define expected behavior. Next, use a minimal implementation to pass the test. Finally, organize the code structure.
When to Use
- Adding or modifying core logic.
- Fixing bugs and needing regression protection.
- Requirements can be written as explicit input/output acceptance tests.
Workflow
- Red: Write a failing test describing the expected behavior.
- Green: Write the minimal code to make the test pass.
- Refactor: Clean up naming, structure, and duplication.
- Repeat the cycle until acceptance criteria are met.
Ironclad Rules
- Do NOT write massive amounts of features before writing tests.
- Focus on one small goal per cycle.
- All tests MUST pass after refactoring.
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.
- 2d ago First seen · 30 lines · 23 tokens per session scan A 762ab7b7099c
test-driven-development is a skill published in the GitHub repository KbWen/agentic-os (149 stars, last pushed 8d ago), licensed MIT. It adds 23 tokens to every session and 207 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-30.
Other skills, from other repositories
tdd
AI DevKit · Test-driven development — write a failing test before writing production code. Use when implementing new functionality, adding behavior, or fixing bugs during active development.
orloj-generator
Interactive scaffold generator for Orloj multi-agent systems. Use this skill whenever someone wants to create, set up, scaffold, bootstrap, or generate an Orloj agent system, pipeline, swarm, or hierarchy. Also trigger when users mention "orlojctl init", ask how to get started with Orloj, want to build a multi-agent…
auto-fix
버그 수정 — 재현과 최소 수정 중심으로 문제를 해결합니다.
tdd-test-engineer
Use for test-first development, regression tests, flaky test debugging, coverage gaps, test strategy, CI failures, or converting bugs into minimal reproducible tests.
debugging
체계적 디버깅 및 버그 수정 스킬.
implement
Write the production code that makes a pre-decided set of failing tests pass, within an explicit writeset, following an explicit behavior contract. Used by /tdd Step 3 and by /swarm-dispatch workers. The caller has already decided architecture, naming, file layout, and abstraction boundaries — this skill executes that…