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/junghwayang/oh-my-codex/tddnpx skills add junghwaYang/oh-my-codex --skill tddgit clone --depth 1 https://github.com/junghwaYang/oh-my-codexWrote 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/junghwayang/oh-my-codex/tdd)<a href="https://agentmods.dev/skills/junghwayang/oh-my-codex/tdd"><img src="https://agentmods.dev/badge/skills/junghwayang/oh-my-codex/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 | $0.00000 | $0.00697 |
| Opus 5 | $0.00000 | $0.00349 |
| Sonnet 5 | $0.00000 | $0.00139 |
| Haiku 4.5 | $0.00000 | $0.00070 |
Grade A, and why
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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Skill
Test-Driven Development workflow.
When to Use
- Building new features with clear requirements
- Refactoring with safety net
- Bug fixes (reproduce first, then fix)
- When code correctness is critical
When NOT to Use
- Exploratory prototyping
- UI/visual development
- One-off scripts
TDD Cycle
┌─────────────────┐
│ RED │
│ Write a │
│ failing test │
└────────┬────────┘
│
▼
┌─────────────────┐
│ GREEN │
│ Make it │
│ pass │
└────────┬────────┘
│
▼
┌─────────────────┐
│ REFACTOR │
│ Clean up │
│ the code │
└────────┬────────┘
│
└──────────→ (repeat)
Workflow
1. RED - Write Failing Test
// Write the test FIRST
test('should calculate total with tax', () => {
const cart = new Cart();
cart.add({ price: 100 });
expect(cart.totalWithTax(0.1)).toBe(110);
});
Run test → Should FAIL (function doesn't exist yet)
2. GREEN - Minimal Implementation
// Write JUST enough to pass
class Cart {
items = [];
add(item) { this.items.push(item); }
totalWithTax(rate) {
const subtotal = this.items.reduce((sum, i) => sum + i.price, 0);
return subtotal * (1 + rate);
}
}
Run test → Should PASS
3. REFACTOR - Improve
// Now clean up
class Cart {
private items: CartItem[] = [];
add(item: CartItem): void {
this.items.push(item);
}
get subtotal(): number {
return this.items.reduce((sum, item) => sum + item.price, 0);
}
totalWithTax(taxRate: number): number {
return this.subtotal * (1 + taxRate);
}
}
Run test → Should still PASS
Test Structure
describe('Feature', () => {
// Setup
beforeEach(() => { /* reset state */ });
// Happy path
test('should work with valid input', () => {});
// Edge cases
test('should handle empty input', () => {});
test('should handle null', () => {});
// Error cases
test('should throw on invalid input', () => {});
});
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.
- 4d ago First seen · 132 lines · 0 tokens per session scan A 706550218d5d
tdd is a skill published in the GitHub repository junghwaYang/oh-my-codex (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 697 tokens. 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
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
test-first-bugs
Enforces a test-driven bug-fixing workflow. Use when a user reports a bug, failing code, an error, or asks to fix something.
growing-outside-in-systems
Drive feature development using Outside-In TDD with Hexagonal Architecture. Design emerges through inline code, in-memory fakes, interface extraction, and deferred I/O. Use when building features, writing tests, or structuring backend services. Triggers on: TDD, outside-in, hexagonal, ports and adapters, emergent…
plan-create
Create structured implementation plans for autonomous TDD development. Use for new features, multi-file changes, or anything requiring multiple steps or tests. Triggers on aspirational openers ("let's build", "let's start building", "I want to make", "I want an app that", "help me build"), capability lists ("users…
red-green-refactor
Guides the red-green-refactor TDD workflow: write a failing test first, implement the minimum code to make it pass, then refactor while keeping tests green. Use when a user asks to practice TDD, write tests first, follow red-green-refactor, do test-driven development, write failing tests before code, or phrases like…
outside-in-tdd
Use when writing tests from the outside-in, defining behavior before code, or any feature where tests should start from observable business behavior and let internal design emerge.