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 selmakcby/claude-agents-skills --skill tddgit clone --depth 1 https://github.com/selmakcby/claude-agents-skillsWrote 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/selmakcby/claude-agents-skills/tdd)<a href="https://agentmods.dev/skills/selmakcby/claude-agents-skills/tdd"><img src="https://agentmods.dev/badge/skills/selmakcby/claude-agents-skills/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/selmakcby/claude-agents-skills/tdd"><img src="https://agentmods.dev/badge/skills/selmakcby/claude-agents-skills/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.00040 | $0.00406 |
| Opus 5 | $0.00020 | $0.00203 |
| Sonnet 5 | $0.00008 | $0.00081 |
| Haiku 4.5 | $0.00004 | $0.00041 |
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 11d 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-Driven Development
Ne zaman tetiklenir
- Yeni özellik yazıldığında
- Bug fix öncesi (hatayı üreten test ilk yazılır)
- Refactor sırasında (mevcut testler yeşil kalmalı)
RED — GREEN — REFACTOR
1. RED — Önce başarısız test yaz
- Yeni davranışı test olarak yaz
- Testi çalıştır, başarısız olduğunu gör
- Başarısız olmazsa, test gerçekten bir şey ölçmüyor demektir
2. GREEN — Minimum kodu yaz
- Testi geçiren en az kodu yaz
- Güzel olmasına çalışma, sadece geçsin
- Testin geçtiğini doğrula
3. REFACTOR — Temizle
- Kod çalışıyor, şimdi netleştir
- Testler yeşil kalmalı
- İsim düzelt, duplication kaldır, fonksiyonları böl
Kapsam hedefleri
- Genel kod: %80+ coverage
- Kritik: auth, ödeme, güvenlik → %100 coverage
- Test türleri (hepsi gerekli):
- Unit (fonksiyon/utility)
- Integration (API, DB)
- E2E (kritik kullanıcı akışları)
Kurallar
- Önce test, sonra kod. İstisnasız.
- Test başarısız olursa kodu düzelt — testi düzeltme
- Tüm dış bağımlılıkları mock'la (DB, API'ler, 3. parti)
- Testler bağımsız olmalı (state paylaşmamalı)
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.
- 11d ago First seen · 45 lines · 40 tokens per session scan A c017fb136a75
tdd is a skill published in the GitHub repository selmakcby/claude-agents-skills (124 stars, last pushed 4mo ago), licensed MIT. It adds 40 tokens to every session and 406 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-30.
Other skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.
python
Python development with ruff, mypy, pytest - TDD and type safety.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.