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 tolgakisaogullari/SumelaOS --skill test-driven-developmentgit clone --depth 1 https://github.com/tolgakisaogullari/SumelaOSWrote 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/tolgakisaogullari/sumelaos/test-driven-development)<a href="https://agentmods.dev/skills/tolgakisaogullari/sumelaos/test-driven-development"><img src="https://agentmods.dev/badge/skills/tolgakisaogullari/sumelaos/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.
<a href="https://agentmods.dev/skills/tolgakisaogullari/sumelaos/test-driven-development"><img src="https://agentmods.dev/badge/skills/tolgakisaogullari/sumelaos/test-driven-development.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.00023 | $0.00498 |
| Opus 5 | $0.00012 | $0.00249 |
| Sonnet 5 | $0.00005 | $0.00100 |
| Haiku 4.5 | $0.00002 | $0.00050 |
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.
What it actually says
<tdd_workflow> If the user approved TDD, execute this cycle strictly in order for EVERY behavior change or bugfix:
- RED (Write Failing Test): Write a single, minimal test demonstrating the desired behavior or reproducing the bug. Test actual behavior, not mock behavior. Where applicable, include tests for security constraints and edge cases based on the
secure-coding-standard. - VERIFY RED (Watch It Fail): Run the test. You MUST verify that it fails specifically because the feature is missing or the bug exists (not due to syntax or setup errors).
- GREEN (Minimal Code): Write the absolute minimum implementation code required to make the test pass. Actively apply
secure-coding-standardprinciples while writing this code. Do not over-engineer or add unrequested features (YAGNI). - VERIFY GREEN (Watch It Pass): Run the test suite. Ensure the new test passes and no existing tests are broken.
- REFACTOR (Clean Up): Only after the test is green, refactor the code to remove duplication and improve names. Tests must remain green. </tdd_workflow>
<testing_constraints>
- CONDITIONAL RATIONALIZATION: If the user opted INTO TDD, do not skip it for "simple" changes, emergencies, or refactoring. Strict compliance is required.
- AVOID MOCKS: Test real logic whenever possible.
- NO TEST POLLUTION: Never add test-only methods or variables to production code.
- SECURITY COVERAGE: Ensure authentication, input validation, and boundary limits are tested if writing tests for secure features.
- REFERENCE: Consult
./testing-anti-patterns.mdbefore adding mocks or complex test utilities. </testing_constraints>
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.
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.
- 9d ago First seen · 28 lines · 23 tokens per session scan A 8fd5d814ce30
test-driven-development is a skill published in the GitHub repository tolgakisaogullari/SumelaOS (4 stars, last pushed 14d ago), licensed MIT. It adds 23 tokens to every session and 498 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-31.
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.