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 synaptiai/synapti-marketplace --skill tdd-patternsgit clone --depth 1 https://github.com/synaptiai/synapti-marketplaceWrote 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/synaptiai/synapti-marketplace/tdd-patterns)<a href="https://agentmods.dev/skills/synaptiai/synapti-marketplace/tdd-patterns"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/tdd-patterns/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/synaptiai/synapti-marketplace/tdd-patterns"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/tdd-patterns.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.00114 | $0.01713 |
| Opus 5 | $0.00057 | $0.00856 |
| Sonnet 5 | $0.00023 | $0.00343 |
| Haiku 4.5 | $0.00011 | $0.00171 |
Grade A, and why
tdd-patterns 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 6d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Patterns
Domain skill for test-driven development: Red-Green-Refactor cycle, test quality, and runner discipline.
Iron Law
IF YOU DIDN'T WATCH THE TEST FAIL, YOU DON'T KNOW IF IT TESTS THE RIGHT THING.
A test that has never failed might pass for the wrong reason. The RED phase exists to prove the test is valid.
Red-Green-Refactor Cycle
For each feature or fix, track the TDD cycle with tasks:
TaskCreate("RED: Write failing test for {behavior}", "Minimal test describing desired behavior. MUST fail on first run.")
TaskCreate("GREEN: Implement {behavior}", "Simplest code to make the test pass. No cleverness.")
TaskCreate("REFACTOR: Clean up {behavior}", "Improve quality. All tests must still pass after each step.")
RED: Write a Failing Test
TaskUpdate(RED task, status: "in_progress")
- Write the minimal test that describes the desired behavior
- Run it — it MUST fail
- Verify it fails for the right reason (not a syntax error, not wrong import)
TaskUpdate(RED task, status: "completed")
GREEN: Make It Pass
TaskUpdate(GREEN task, status: "in_progress")
- Write the simplest code that makes the test pass
- No cleverness. No optimization. No "while I'm here" improvements.
- Run the test — it MUST pass now
TaskUpdate(GREEN task, status: "completed")
REFACTOR: Clean Up
TaskUpdate(REFACTOR task, status: "in_progress")
- Improve code quality (naming, structure, duplication)
- Run ALL tests after each refactor step — they must still pass
- No new functionality during refactor — that's a new RED phase
TaskUpdate(REFACTOR task, status: "completed") Use TaskList to confirm the full cycle completed before moving to the next behavior.
The cycle is non-negotiable. RED → GREEN → REFACTOR. Always in this order.
Test Runner Discipline
Always use run mode, never watch mode:
| Framework | Correct | Wrong |
|---|---|---|
| Vitest | vitest run |
vitest (watch) |
| Jest | CI=true jest or jest --watchAll=false |
jest (watch) |
| Pytest | pytest |
— |
| RSpec | rspec |
guard (watch) |
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.
- 6d ago First seen · 184 lines · 114 tokens per session scan A bade84298b26
tdd-patterns is a skill published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 114 tokens to every session and 1,713 once invoked, about $0.0006 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-09-03.
Other skills, from other repositories
x-qdev
A compact development workflow for a small, clearly defined code change. It keeps the requirement, initially failing tests, implementation, and real verification results in one task document, following TDD, or test-driven development.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
story-development
Implement user stories with test-driven development methodology.
auto-loop
TDD-based autonomous development loop with checkpoint recovery and observability changelog.
workflow
Run the complete 5-step development workflow: focus problem → prevent over-development → test-first (TDD) → document → smart commit. Use when starting a new feature, or when the user runs /workflow or asks for the full development flow.
test-first
Drive one feature through a strict TDD Red-Green-Refactor cycle with checklists for each phase. Use when implementing new functionality test-first, or when the user runs /test-first.