test-driven-development

test-driven-development is a skill for Claude Code, Codex from bl1nk-bot/bl1nk-agents-manager. It costs 17 tokens per session (2,414 once invoked), scanned A, a copy of compose:tdd, MIT.

แนวทางการพัฒนาซอฟต์แวร์แบบ TDD หรือการเขียนการทดสอบก่อนเขียนโค้ดจริง โดยเริ่มจากทดสอบที่ล้มเหลว แล้วเขียนโค้ดให้น้อยที่สุดเพื่อให้ผ่าน

In plain words
What is it for?
ใช้กับการทำฟีเจอร์ใหม่ แก้บั๊ก ปรับโครงสร้างโค้ด และเปลี่ยนพฤติกรรม โดยทำตามวงจรเขียนทดสอบที่ล้มเหลว แก้ให้ผ่าน แล้วค่อยปรับปรุงโค้ด
Why use it?
ช่วยยืนยันว่าการทดสอบตรวจพฤติกรรมที่ต้องการจริง และลดความเสี่ยงจากฟีเจอร์ใหม่ บั๊ก การปรับโครงสร้าง หรือการเปลี่ยนพฤติกรรม

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit ใช้กับการทำฟีเจอร์ใหม่ แก้บั๊ก ปรับโครงสร้างโค้ด และเปลี่ยนพฤติกรรม โดยทำตามวงจรเขียนทดสอบที่ล้มเหลว แก้ให้ผ่าน แล้วค่อยปรับปรุงโค้ด

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bl1nk-bot/bl1nk-agents-manager/test-driven-development
Install

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.

Any agent
npx skills add bl1nk-bot/bl1nk-agents-manager --skill test-driven-development
Clone the repo
git clone --depth 1 https://github.com/bl1nk-bot/bl1nk-agents-manager

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for test-driven-development

README.md
[![agentmods](https://agentmods.dev/badge/skills/bl1nk-bot/bl1nk-agents-manager/test-driven-development/github.svg)](https://agentmods.dev/skills/bl1nk-bot/bl1nk-agents-manager/test-driven-development)
Your own site
<a href="https://agentmods.dev/skills/bl1nk-bot/bl1nk-agents-manager/test-driven-development"><img src="https://agentmods.dev/badge/skills/bl1nk-bot/bl1nk-agents-manager/test-driven-development/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.

agentmods 80×15 button for test-driven-development

Your own site · 80×15
<a href="https://agentmods.dev/skills/bl1nk-bot/bl1nk-agents-manager/test-driven-development"><img src="https://agentmods.dev/badge/skills/bl1nk-bot/bl1nk-agents-manager/test-driven-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,414 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 89% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00017 $0.02414
Opus 5 $0.00009 $0.01207
Sonnet 5 $0.00003 $0.00483
Haiku 4.5 $0.00002 $0.00241

Measured 9d ago against content hash 577cbc3ceb7b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

test-driven-development 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 9d 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.

Origin

This is a copy

89% identical to compose:tdd — 82 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/test-driven-development/SKILL.md · 374 lines

How it starts

The opening of the file, as written. The whole thing — 374 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Test-Driven Development (TDD)

Overview

Write the test first. Watch it fail. Write minimal code to pass.

Core principle: If you didn't watch the test fail, you don't know if it tests the right thing.

Violating the letter of the rules is violating the spirit of the rules.

When to Use

Always:

  • New features
  • Bug fixes
  • Refactoring
  • Behavior changes

Exceptions (ask your human partner):

  • Throwaway prototypes
  • Generated code
  • Configuration files

Thinking "skip TDD just this once"? Stop. That's rationalization.

The Iron Law

NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST

Write code before the test? Delete it. Start over.

No exceptions:

  • Don't keep it as "reference"
  • Don't "adapt" it while writing tests
  • Don't look at it
  • Delete means delete

Implement fresh from tests. Period.

Red-Green-Refactor

digraph tdd_cycle {
    rankdir=LR;
    red [label="RED\nWrite failing test", shape=box, style=filled, fillcolor="#ffcccc"];
    verify_red [label="Verify fails\ncorrectly", shape=diamond];
    green [label="GREEN\nMinimal code", shape=box, style=filled, fillcolor="#ccffcc"];
    verify_green [label="Verify passes\nAll green", shape=diamond];
    refactor [label="REFACTOR\nClean up", shape=box, style=filled, fillcolor="#ccccff"];
    next [label="Next", shape=ellipse];

    red -> verify_red;
    verify_red -> green [label="yes"];
    verify_red -> red [label="wrong\nfailure"];
    green -> verify_green;
    verify_green -> refactor [label="yes"];
    verify_green -> green [label="no"];
    refactor -> verify_green [label="stay\ngreen"];
    verify_green -> next;
    next -> red;
}
```text
### RED - Write Failing Test

Write one minimal test showing what should happen.

<Good>
```typescript
test('retries failed operations 3 times', async () => {
  let attempts = 0;
  const operation = () => {
    attempts++;
    if (attempts < 3) throw new Error('fail');
    return 'success';
  };

  const result = await retryOperation(operation);

  expect(result).toBe('success');
  expect(attempts).toBe(3);
});

```text
Clear name, tests real behavior, one thing
</Good>

Read the full file on GitHub · 374 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 9d ago First seen · 374 lines · 17 tokens per session scan A 577cbc3ceb7b

Subscribe to this mod's changes

test-driven-development is a skill published in the GitHub repository bl1nk-bot/bl1nk-agents-manager (8 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 2,414 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to compose:tdd, differing in 82 lines, and is treated as a copy.

Related

Other skills, from other repositories

engineering-workflow

A Chinese-language workflow for reliable software development. It describes exploring the problem, making a plan, using TDD (test-driven development, where tests are written before the code), debugging methodically, reviewing code, and verifying the result.

TencentCloud/Octop · 47 tokens

skillgrade-graders

Authors deterministic and LLM rubric graders for skillgrade evaluations. Use when creating scoring scripts, writing evaluation rubrics, or combining multiple graders with weighted scoring. Don't use for setting up eval pipelines, configuring eval.yaml defaults, or general test writing.

mgechev/skillgrade · 54 tokens

skillgrade-setup

Sets up and runs skillgrade evaluation pipelines for Agent Skills. Use when initializing eval configurations, running trials, reviewing results, or integrating with CI. Don't use for writing grader scripts, general test authoring, or non-agentic documentation.

mgechev/skillgrade · 52 tokens

08-debug

Reproduce and fix a known bug, or find an unknown root cause by hypothesis validation. Use when the user wants to fix a bug, find why something breaks, or reopen a stuck investigation. Not for building a feature or reviewing a diff.

ai-driven-dev/framework · 52 tokens

implement

Implement a technical design by decomposing it into dependency-ordered vertical slices, executing each with TDD red-green, reviewing each via an isolated sub-agent, and persisting progress to a state file so work survives session restarts. Use when the user has a tech design (doc or settled conversation) and says…

open-octo/octo-agent · 97 tokens

test-driven-development

TDD: enforce RED-GREEN-REFACTOR, tests before code.

HezaoHezao/poirot · 20 tokens