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 zszz3/AgentRecall --skill test-driven-developmentgit clone --depth 1 https://github.com/zszz3/AgentRecallWrote 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/zszz3/agentrecall/test-driven-development)<a href="https://agentmods.dev/skills/zszz3/agentrecall/test-driven-development"><img src="https://agentmods.dev/badge/skills/zszz3/agentrecall/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/zszz3/agentrecall/test-driven-development"><img src="https://agentmods.dev/badge/skills/zszz3/agentrecall/test-driven-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 67 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
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.00041 | $0.00521 |
| Opus 5.5 | $0.00016 | $0.00208 |
| Sonnet 5.5 | $0.00008 | $0.00104 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade B, and why
test-driven-development scanned grade B with 1 finding 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
- Focused tests and relevant regressions pass without warnings. How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test-Driven Development
Core rule
NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST
Tests written after implementation describe what was built. Tests written first define what should be built and prove that the test can catch its absence.
Red, green, refactor
1. Red
Write one small test for one observable behavior.
- Use a name that states the expected result.
- Exercise real code. Mock only boundaries that cannot be used safely or deterministically.
- Prefer public behavior over private methods, internal call counts, CSS details, or implementation structure.
- Use temporary homes, prefixes, databases, and synthetic fixtures for filesystem or installation behavior.
Run only the new test. Confirm that it fails because the requested behavior is missing. A syntax error, invalid fixture, missing dependency, or unrelated crash is not a valid red state.
If the test passes immediately, it does not demonstrate the new requirement. Correct the test before writing production code.
2. Green
Write the smallest implementation that satisfies the failing behavior.
- Change one cause at a time.
- Do not add speculative options or unrelated cleanup.
- Do not weaken the assertion to fit the implementation.
Run the new test again and confirm it passes. Then run the nearest relevant test set to catch regressions.
3. Refactor
Only after green:
- Remove duplication.
- Improve names and boundaries.
- Simplify control flow.
- Keep behavior unchanged and rerun the tests.
Repeat the cycle for the next behavior.
Bug fixes
Reproduce the original symptom in a test before changing the fix site. The test must fail for the observed reason and pass after the root cause is fixed. When practical, temporarily revert the fix once to confirm the regression test turns red again.
Exceptions
Generated files and data-only metadata do not need artificial unit tests, but the code that loads or validates them does. Throwaway exploration must be discarded before production work begins. Ask the user before intentionally skipping test-first implementation.
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 · 69 lines · 41 tokens per session scan B 474ae635a062
test-driven-development is a skill published in the GitHub repository zszz3/AgentRecall (594 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 521 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.
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…
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.