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 HumanDealer/vibeproof --skill tddgit clone --depth 1 https://github.com/HumanDealer/vibeproofWrote 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/humandealer/vibeproof/tdd)<a href="https://agentmods.dev/skills/humandealer/vibeproof/tdd"><img src="https://agentmods.dev/badge/skills/humandealer/vibeproof/tdd/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/humandealer/vibeproof/tdd"><img src="https://agentmods.dev/badge/skills/humandealer/vibeproof/tdd.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.00060 | $0.00445 |
| Opus 5 | $0.00030 | $0.00222 |
| Sonnet 5 | $0.00012 | $0.00089 |
| Haiku 4.5 | $0.00006 | $0.00044 |
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 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 — test first, then code
The difference between looking senior (running tests) and being senior: the test is written first and defines what correct means. A non-coder can't read the implementation — but they can read "given a logged-out user, the page redirects to login" and confirm that's what they wanted.
The loop (per build step in PLAN.md)
- RED — write the test from the PLAN test list. Run it. Watch it FAIL. A test that passes before you write code tests nothing. Confirm it fails for the right reason.
- GREEN — write the minimum code to make it pass. Run it. Watch it PASS.
- REFACTOR — clean the code (names, duplication, clarity) with the test still green. This is where "clean code a Meta senior would write" happens.
- Check the box in PLAN.md. Next step.
Rules
- One behavior per test. Name it so a non-coder understands:
test_logged_out_user_redirects_to_login. - Never delete a failing test to make the bar green. Fix the code or the spec.
- No
skip/xfailwithout a comment + reason. A skipped test is a lie about coverage. - New or changed behavior → a test exercises it. If
vibeproof checklater shows tests passing but you wrote no test, you skipped the contract.
Verify
After GREEN, run vibeproof check. The verdict line must show tests passing with
a real count (e.g. tests ok: 14 passed), not 0 passed or skipped.
Next: build the remaining steps, then /ship.
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 · 36 lines · 60 tokens per session scan A bea02cd213d8
tdd is a skill published in the GitHub repository HumanDealer/vibeproof (2 stars, last pushed 3mo ago), licensed MIT. It adds 60 tokens to every session and 445 once invoked, about $0.0003 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
TDD workflow - red-green-refactor per docs/methodology/tdd.md. Use when asked to '/tdd', 'TDD workflow', 'red-green-refactor', 'test-first development', 'write the failing test first'.
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.
writing-skills
A guide for creating and testing reusable instructions for AI agents, called skills. It applies test-driven development, or TDD—the practice of writing tests before implementation—to instruction documents.
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.