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/raidriar7170/hermes-skilleval/test-driven-developmentnpx skills add Raidriar7170/hermes-skilleval --skill test-driven-developmentgit clone --depth 1 https://github.com/Raidriar7170/hermes-skillevalWrote 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/raidriar7170/hermes-skilleval/test-driven-development)<a href="https://agentmods.dev/skills/raidriar7170/hermes-skilleval/test-driven-development"><img src="https://agentmods.dev/badge/skills/raidriar7170/hermes-skilleval/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.1 | $0.00022 | $0.00288 |
| Opus 5 | $0.00011 | $0.00144 |
| Sonnet 5 | $0.00004 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
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 6d 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
Use when implementing a feature, bug fix, or refactor that can be described by a test. Start with a focused failing test, confirm the failure reason, implement the minimal code, and rerun the test until it passes.
Evidence
- Failing test output before the fix.
- Passing targeted test after implementation.
- Notes on any skipped broader validation.
Source Snapshot
Source: superpowers/test-driven-development/SKILL.md
Short excerpt used for provenance, not a full source copy.
# Test-Driven Development (TDD) ## Overview Write the test first. Watch it fail. Write
minimal code to pass. **Core principle:** If you didn't watch the test fail, you don't
know if it tests the right thing. **Violating the letter of the rules is violating the
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.
- 6d ago First seen · 35 lines · 22 tokens per session scan A d1a918c9bfdc
Test Driven Development is a skill published in the GitHub repository Raidriar7170/hermes-skilleval (124 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 288 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.
Other skills, from other repositories
codspeed-optimize
Autonomously optimize code for performance using CodSpeed benchmarks, flamegraph analysis, and iterative improvement. Use this skill whenever the user wants to make code faster, reduce CPU usage, optimize memory, improve throughput, find performance bottlenecks, or asks to 'optimize', 'speed up', 'make faster'…
codspeed-setup-harness
Set up performance benchmarks and CodSpeed harness for a project. Use this skill whenever the user wants to create benchmarks, add performance tests, set up CodSpeed, configure codspeed.yml, integrate a benchmarking framework (criterion, divan, pytest-benchmark, vitest bench, go test -bench, google benchmark), or when…
building
Implementation skill for writing production code with TDD. Covers the RED-GREEN-REFACTOR cycle, false-RED detection, vertical slicing, scope escalation, test process discipline, and code generation patterns. Loaded by component-builder and bug-investigator.
test-driven-development
Implements behavior changes with a test-first red-green-refactor loop: write one meaningful failing test, watch it fail for the intended reason, make the smallest change, then refactor while green. Use for new behavior, bug fixes, refactors with preserved contracts, and regression tests. Not required for disposable…
custom-agent-creator
Create and integrate new modular agents for browseruse-bench (BaseAgent in browserusebench/agents/, registry import in init.py, entry in configs/agentregistry.yaml, runtime config in root config.yaml agents section). Use when a user asks to add/register a new agent, scaffold a custom agent, or implement a new agent…
bubench-run
Use this skill whenever the user describes a benchmark experiment using any combination of these parameters — agent (e.g. browser-use, skyvern), model (e.g. deepseek, minimax, claude, gemini, gpt), data/benchmark (e.g. LexBench-Browser), browser (e.g. Chrome-Local, lexmount), and tasks (specific IDs or "all"). Trigger…