test-driven-development

A test-first development process called TDD, where tests are written and used throughout the change. The cycle is red, green, refactor: first a test fails, then the code makes it pass, then the code is improved.

In plain words
What is it for?
Implementing tasks that need a documented test loop, including failing-test, passing-test, refactoring, final-pass, and test-quality evidence.
Why use it?
It provides evidence that the change works and that the tests meaningfully check it. It also requires a final passing run after refactoring.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/gobbyai/gobby/test-driven-development
Any agent
npx skills add GobbyAI/gobby --skill test-driven-development
Clone the repo
git clone --depth 1 https://github.com/GobbyAI/gobby

Made for: Claude Code, Codex.

Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 317 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found 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 $0.00027 $0.00317
Opus 5 $0.00014 $0.00159
Sonnet 5 $0.00005 $0.00063
Haiku 4.5 $0.00003 $0.00032

Measured 2d ago against content hash 05bbcfbf69b3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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.

src/gobby/install/shared/skills/test-driven-development/SKILL.md · 43 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. 2d ago First seen · 43 lines · 27 tokens per session scan A 05bbcfbf69b3

Subscribe to this mod's changes

test-driven-development is a skill published in the GitHub repository GobbyAI/gobby (19 stars, last pushed 4d ago), with no licence file. It adds 27 tokens to every session and 317 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

opcore

Use for repository code intelligence and introduced-change validation in Zeroshot.

the-open-engine/zeroshot · 17 tokens

goalify

Hand Claude a huge task. Come back to proof it's done — not a promise that it is. goalify writes the brief (a file with the instructions the run works from) and the condition (a short string you paste into /goal), because /goal takes a condition string, never a file path. Use when the user says "goalify", "goalify…

Aboudjem/goalify · 178 tokens

skillkit

Toolkit for creating and validating skills and subagents. Use when: creating a new skill (fast or full mode), validating an existing skill, deciding Skills vs Subagents, migrating docs to skills, estimating token cost, or running a security scan. Triggers: "create skill", "build skill", "validate skill", "new…

rfxlamia/skillkit · 86 tokens

skillkit-help

Pre-build orientation for skill creators. Answers "what are skills?", "should I make one?", and "is my skill good enough?" before you start building. Use for: understand skills, decide skills vs subagents, validate an existing skill. When ready to actually build, invoke /skillkit directly instead.

rfxlamia/skillkit · 66 tokens

openspec-explore

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

Happenmass/omux · 39 tokens

openspec-apply-change

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

Happenmass/omux · 31 tokens