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 bunhine0452/Ocul-PM --skill tdd-workflowgit clone --depth 1 https://github.com/bunhine0452/Ocul-PMWrote 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/bunhine0452/ocul-pm/tdd-workflow)<a href="https://agentmods.dev/skills/bunhine0452/ocul-pm/tdd-workflow"><img src="https://agentmods.dev/badge/skills/bunhine0452/ocul-pm/tdd-workflow/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/bunhine0452/ocul-pm/tdd-workflow"><img src="https://agentmods.dev/badge/skills/bunhine0452/ocul-pm/tdd-workflow.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.00047 | $0.00610 |
| Opus 5 | $0.00023 | $0.00305 |
| Sonnet 5 | $0.00009 | $0.00122 |
| Haiku 4.5 | $0.00005 | $0.00061 |
Grade A, and why
tdd-workflow 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 10d 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-workflow — 테스트 먼저
절차
- 실패하는 테스트 먼저 — 구현 전에 기대 동작을 테스트로 적고, 실행해 실패를 눈으로 확인한다 (버그 수정이면 재현 테스트). 컴파일 언어에서는 컴파일 실패도 유효한 RED 다 — 아직 없는 API 를 호출하는 테스트가 컴파일되지 않는 것이 정확히 기대 상태다.
- 최소 구현 — 그 테스트를 통과시키는 최소한의 코드만 쓴다.
- 그린 확인 — 새 테스트 + 기존 스위트 전체를 실행해 회귀가 없음을 확인한다.
- 리팩토링 — 그린을 유지하며 정리하고, 끝나면 스위트를 다시 돌린다.
- 다음 동작 단위로 1~4 를 반복한다.
커밋 체크포인트 (권장)
단계 경계마다 커밋을 끊으면 증거가 이력에 남는다: test: <재현/기대> 추가(RED 상태) → fix:/feat: <구현>(GREEN) → refactor: 정리. 스쿼시 머지 후에도 증거가 살아남도록, 마지막에 아래 증거 표를 일지에 남긴다 — ## 검증 은 규격상 1~3줄 요약이므로, 표는 ## 메모 섹션에 두고 검증에는 "TDD 증거 표는 메모 참조" 한 줄로 가리킨다.
증거 표 — 일지 ## 메모 규격
| 보장하는 것 | 테스트 | RED 확인 | GREEN 명령 |
|---|---|---|---|
| 자정 롤오버가 중복 없이 1회 | today_rollover.test.ts | ✓ (수정 전 실패 확인) | pnpm vitest run src/__tests__/today_rollover.test.ts |
- RED 확인 열이 비어 있으면 그 행은 TDD 가 아니다 — 사후 테스트로 정직하게 표기한다.
규칙
- 테스트가 실패하는 것을 보기 전에는 구현을 시작하지 않는다 (통과부터 하는 테스트는 아무것도 증명하지 못한다).
- 테스트를 통과시키려고 테스트를 약화시키지 않는다 — 기대를 바꿔야 하면 이유를 사용자에게 보고한다.
- 커버리지 숫자보다 시나리오: 해피패스 1개 + 에지 케이스 2개 이상을 기본으로 한다.
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.
- 10d ago First seen · 33 lines · 47 tokens per session scan A d73287bd2bca
tdd-workflow is a skill published in the GitHub repository bunhine0452/Ocul-PM (7 stars, last pushed 2d ago), licensed MIT. It adds 47 tokens to every session and 610 once invoked, about $0.0002 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
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-driven-development
Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
test-driven-development
Test-driven development, or TDD, is a way to build software by writing a test that fails, adding the smallest code that makes it pass, and then cleaning up the code. These instructions require that process for features, bug fixes, refactors, and behavior changes.
skillshare-implement-feature
Implement a feature from a spec file or description using TDD workflow. Use this skill whenever the user asks to: add a new CLI command, implement a feature from a spec, build new functionality, add a flag, create a new internal package, or write Go code for skillshare. This skill enforces test-first development…
gentle-ai
Use Gentle AI harness discipline for Pi work: clarify first, preserve OpenSpec artifacts, use strict TDD where available, delegate through subagents when useful, and protect review workload.