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 omnigentx/jarvis --skill test-driven-developmentgit clone --depth 1 https://github.com/omnigentx/jarvisWrote 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/omnigentx/jarvis/test-driven-development)<a href="https://agentmods.dev/skills/omnigentx/jarvis/test-driven-development"><img src="https://agentmods.dev/badge/skills/omnigentx/jarvis/test-driven-development.svg" alt="Measured on agentmods" 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.00028 | $0.00396 |
| Opus 5 | $0.00014 | $0.00198 |
| Sonnet 5 | $0.00006 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00040 |
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 3d 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)
Adapted from obra/superpowers.
Core Rule
NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST
If you wrote code before the test — delete it. Start over. No exceptions.
Red-Green-Refactor Cycle
RED — Write Failing Test
Write ONE minimal test showing what should happen.
- Clear, descriptive test name
- Tests real behavior, not mocks
- One assertion per test
GREEN — Minimal Code to Pass
Write the simplest code that makes the test pass.
- No over-engineering
- No "future-proofing"
- Just enough to go green
REFACTOR — Clean Up
Improve code quality while keeping tests green.
- Extract common patterns
- Improve naming
- Remove duplication
When to Use
Always:
- New features
- Bug fixes
- Behavior changes
Exceptions (discuss with team first):
- Throwaway prototypes
- Configuration files
- Generated code
Anti-Patterns
- ❌ Writing tests after implementation
- ❌ Keeping "reference" code you wrote before tests
- ❌ Over-engineering with options/config nobody asked for (YAGNI)
- ❌ Testing mock behavior instead of real behavior
- ❌ Skipping the "watch it fail" step
In Meeting Context
When implementing with TDD in a meeting:
- Write the test first — show it in your
speak() - Run it — show it fails
- Write minimal implementation
- Run it — show it passes
- Report results to QE for review
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.
- 3d ago First seen · 66 lines · 28 tokens per session scan A 35f803401b7e
test-driven-development is a skill published in the GitHub repository omnigentx/jarvis (36 stars, last pushed 11d ago), licensed MIT. It adds 28 tokens to every session and 396 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-09-03.
Other skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
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.
tdd
This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the…
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
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.