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 modimihir07/agentic-os --skill tdd-cyclegit clone --depth 1 https://github.com/modimihir07/agentic-osWrote 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/modimihir07/agentic-os/tdd-cycle)<a href="https://agentmods.dev/skills/modimihir07/agentic-os/tdd-cycle"><img src="https://agentmods.dev/badge/skills/modimihir07/agentic-os/tdd-cycle/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/modimihir07/agentic-os/tdd-cycle"><img src="https://agentmods.dev/badge/skills/modimihir07/agentic-os/tdd-cycle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00014 | $0.00241 |
| Opus 5.5 | $0.00006 | $0.00096 |
| Sonnet 5.5 | $0.00003 | $0.00048 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade A, and why
tdd-cycle 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 1mo 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 Cycle
Description
Enforces the Red-Green-Refactor TDD cycle: write a failing test, make it pass, then refactor. No code is written before a test exists.
When to Use
- When implementing any new feature
- When fixing a bug
- When refactoring existing code
Process
- RED: Write a failing test for the desired behavior
- Verify test fails (confirm test is valid)
- GREEN: Write minimal code to make the test pass
- Verify test passes
- REFACTOR: Clean up code while keeping tests green
- Commit with message format:
RED|GREEN|REFACTOR: description
Rules
- Production code is only written to make a failing test pass
- Delete any code written before tests
- Never skip the RED phase
Agent Assignment
- Primary: opencode
What ships with it
3 files 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.
- 1mo ago First seen · 34 lines · 14 tokens per session scan A b16c6eccf223
tdd-cycle is a skill published in the GitHub repository modimihir07/agentic-os (203 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 241 once invoked, about $0.0001 per session on Opus 5.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
test-driven-development
TDD: enforce RED-GREEN-REFACTOR, tests before code.
plugin-test
A testing guide for Zhin.js plugins using Vitest, a JavaScript and TypeScript testing framework. It focuses on checking command and tool behavior, ordinary business logic, and the plugin package’s required structure.
tdd-workflow
Test-first discipline and what makes a test worth keeping. Use when implementing any feature or bug fix, before writing production code, and whenever writing or changing a test.
java-testing-junit-mockito
Use when writing tests for Java (Quarkus or Spring) code - JUnit Jupiter structure, Mockito for collaborators, test slices, Testcontainers, and framework-native integration tests, test-first.
verify-before-done
Evidence rules for completion claims. Use before ticking an acceptance criterion, ending an implementation run, or writing anything that says something works, passes or is fixed.
analytics-result-qa
Use when you are about to hand off any number, table, chart or analysis someone will act on (a metric query, a dbt mart, a report, an experiment readout) — the pre-delivery checklist for data quality, calculation, reasonableness and presentation, and the pitfalls that produce plausible wrong numbers.