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 Jkudjo/oh-my-cursor --skill tddgit clone --depth 1 https://github.com/Jkudjo/oh-my-cursorWrote 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/jkudjo/oh-my-cursor/tdd)<a href="https://agentmods.dev/skills/jkudjo/oh-my-cursor/tdd"><img src="https://agentmods.dev/badge/skills/jkudjo/oh-my-cursor/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.00018 | $0.00306 |
| Opus 5 | $0.00009 | $0.00153 |
| Sonnet 5 | $0.00004 | $0.00061 |
| Haiku 4.5 | $0.00002 | $0.00031 |
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 8d 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
tdd
Invoke this skill to follow a strict red-green-refactor TDD cycle.
When to use
- Building a new function, module, or feature from scratch
- When you want tests to define the contract before implementation
- Fixing a bug (write a failing test that reproduces it first)
What it does
Red phase
- Read the clarified scope (from memory key
clarified-scopeif available) - Write failing tests that define the expected behavior:
- Happy path
- Edge cases
- Error conditions
- Run the tests — verify they ALL fail (red)
- Do NOT write any implementation yet
Green phase
- Write the minimum implementation to make tests pass
- Run tests — iterate until all pass (green)
- No over-engineering — minimum code only
Refactor phase
- Clean up the implementation without changing behavior
- Run tests again — must still be green
- Commit: "test: add tests for X" then "feat: implement X"
Rules
- Tests are written before implementation — always
- Green phase: minimum code, no extras
- Refactor phase: never change observable behavior
- Never delete or weaken tests to make them pass
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.
- 8d ago First seen · 44 lines · 18 tokens per session scan A df6695d8467b
tdd is a skill published in the GitHub repository Jkudjo/oh-my-cursor (1 stars, last pushed 5mo ago), licensed MIT. It adds 18 tokens to every session and 306 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-31.
Other skills, from other repositories
test-driven-development
Use when implementing any feature, bugfix, or code change - write tests first, watch them fail, then implement.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first.
mushi-integration
Full end-to-end Mushi Mushi integration smoke test: bug capture → AI triage → story mapping → TDD test generation → approval → execution → PDCA cycle. Use when "test mushi integration", "verify full pipeline", "mushi e2e check", "does mushi work end-to-end", "smoke test mushi", or after deploying changes.
testing
TDD, mocks, gauntlet, regression naming. Use when writing or expanding tests, not because testing.mdc is on.
role-产品开发协调者
A product-development coordinator role that identifies the kind of work requested, chooses the order of tasks, and assigns the right specialist roles.
testing-pyramid
Test Distribution Analysis Command 🧪.