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 agentmods add skills/kareemessam09/openship-app/test-driven-developmentnpx skills add kareemessam09/Openship-App --skill test-driven-developmentgit clone --depth 1 https://github.com/kareemessam09/Openship-AppWrote 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/kareemessam09/openship-app/test-driven-development)<a href="https://agentmods.dev/skills/kareemessam09/openship-app/test-driven-development"><img src="https://agentmods.dev/badge/skills/kareemessam09/openship-app/test-driven-development.svg" alt="Measured on agentmods" 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 | $0.00055 | $0.00451 |
| Opus 5 | $0.00028 | $0.00226 |
| Sonnet 5 | $0.00011 | $0.00090 |
| Haiku 4.5 | $0.00006 | $0.00045 |
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 4d 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
Test-Driven Development (TDD) Superpower
Enforces a disciplined RED-GREEN-REFACTOR cycle.
Core Rules
- Never write production code before a failing test exists.
- Every test must fail first for the expected reason (verify the failure output).
- Write the minimum code necessary to pass the test.
- Refactor with the safety net of passing tests.
The TDD Cycle
┌────────────────────────────────────────────────┐
│ 1. RED: Write a small, targeted failing test │
└──────────────────────┬─────────────────────────┘
▼
┌────────────────────────────────────────────────┐
│ 2. VERIFY: Run the test and observe failure │
└──────────────────────┬─────────────────────────┘
▼
┌────────────────────────────────────────────────┐
│ 3. GREEN: Write minimal code to pass test │
└──────────────────────┬─────────────────────────┘
▼
┌────────────────────────────────────────────────┐
│ 4. REFACTOR: Clean up code while tests stay 🟢 │
└────────────────────────────────────────────────┘
Checklist for Each Feature / Fix
- Define the specific behavior or contract to test.
- Place tests in the corresponding source set (e.g.
shared/src/commonTest/kotlin/...). - Run test using
./gradlew :shared:allTestsor./gradlew testDebugUnitTest. - Confirm failure is due to missing logic, not compilation/syntax errors.
- Implement the simplest logic to make the test pass.
- Verify test passes.
- Refactor formatting, naming, and structure without altering test behavior.
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.
- 4d ago First seen · 46 lines · 55 tokens per session scan A 324337699e6a
test-driven-development is a skill published in the GitHub repository kareemessam09/Openship-App (11 stars, last pushed 8d ago), licensed Apache-2.0. It adds 55 tokens to every session and 451 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-30.
Other skills, from other repositories
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-first-bugs
Enforces a test-driven bug-fixing workflow. Use when a user reports a bug, failing code, an error, or asks to fix something.
tdd
Test-driven development (TDD) process used when writing code. Use whenever you are adding any new code, unless the user explicitly asks to skip TDD or the code is exploratory/spike.
growing-outside-in-systems
Drive feature development using Outside-In TDD with Hexagonal Architecture. Design emerges through inline code, in-memory fakes, interface extraction, and deferred I/O. Use when building features, writing tests, or structuring backend services. Triggers on: TDD, outside-in, hexagonal, ports and adapters, emergent…
plan-create
Create structured implementation plans for autonomous TDD development. Use for new features, multi-file changes, or anything requiring multiple steps or tests. Triggers on aspirational openers ("let's build", "let's start building", "I want to make", "I want an app that", "help me build"), capability lists ("users…
red-green-refactor
Guides the red-green-refactor TDD workflow: write a failing test first, implement the minimum code to make it pass, then refactor while keeping tests green. Use when a user asks to practice TDD, write tests first, follow red-green-refactor, do test-driven development, write failing tests before code, or phrases like…