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/nizos/tdd-guard/setupnpx skills add nizos/tdd-guard --skill setupgit clone --depth 1 https://github.com/nizos/tdd-guardWrote 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/nizos/tdd-guard/setup)<a href="https://agentmods.dev/skills/nizos/tdd-guard/setup"><img src="https://agentmods.dev/badge/skills/nizos/tdd-guard/setup.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 | $0.00039 | $0.01396 |
| Opus 5 | $0.00019 | $0.00698 |
| Sonnet 5 | $0.00008 | $0.00279 |
| Haiku 4.5 | $0.00004 | $0.00140 |
Grade A, and why
setup 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Guard Setup
Set up TDD Guard for the current project. Your goal is to:
- Identify the test framework(s) used in this project
- Install the matching TDD Guard reporter, or update it if already present
- Configure the reporter, or migrate an existing configuration to match the current specification
Reporter packages
| Framework | Reporter package | Registry |
|---|---|---|
| Vitest | tdd-guard-vitest | npm |
| Jest | tdd-guard-jest | npm |
| Storybook | tdd-guard-storybook | npm |
| pytest | tdd-guard-pytest | PyPI |
| PHPUnit | tdd-guard/phpunit | Packagist |
| Go | github.com/nizos/tdd-guard/reporters/go/cmd/tdd-guard-go | go install |
| Rust | tdd-guard-rust | crates.io |
| RSpec | tdd-guard-rspec | RubyGems |
| Minitest | tdd-guard-minitest | RubyGems |
Reporter configuration
All reporters write test results to .claude/tdd-guard/data/test.json relative to the project root.
Vitest — Add the reporter entry to the reporters array with projectRoot in the options object.
reporters: [
'default',
['tdd-guard-vitest', { projectRoot: '/absolute/path/to/project' }],
]
Jest — Add reporter entry to the reporters array with projectRoot option.
reporters: [
'default',
['tdd-guard-jest', { projectRoot: '/absolute/path/to/project' }],
]
Storybook — Construct StorybookReporter in .storybook/test-runner.ts and wire it into the postVisit hook.
// .storybook/test-runner.ts
import { StorybookReporter } from 'tdd-guard-storybook'
const reporter = new StorybookReporter({
projectRoot: '/absolute/path/to/project',
})
module.exports = {
async postVisit(page, context) {
await reporter.onStoryResult(context)
},
}
process.on('exit', () => {
reporter.onComplete()
})
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.
- 4d ago First seen · 151 lines · 39 tokens per session scan A 1a5786af139b
setup is a skill published in the GitHub repository nizos/tdd-guard (2,328 stars, last pushed 18d ago), licensed MIT. It adds 39 tokens to every session and 1,396 once invoked, about $0.0002 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
tdd-rust
TDD workflow for RTK filter development. Red-Green-Refactor with Rust idioms. Real fixtures, token savings assertions, snapshot tests with insta. Auto-triggers on new filter implementation.
rtk-tdd
Enforces TDD (Red-Green-Refactor) for Rust development. Auto-triggers on implementation, testing, refactoring, and bug fixing tasks. Provides Rust-idiomatic testing patterns with anyhow/thiserror, cfg(test), and Arrange-Act-Assert workflow.
software-code-refactoring
Improve production code quality while preserving all existing test behavior. Commonly used for the Refactor phase of TDD red-green-refactor, but applicable to any codebase with tests. Use when production code works but needs cleanup — reducing duplication, improving naming, simplifying complexity, aligning with…
linked-intent-dev
Guide for linked-intent development (LID). Consult for ALL code changes. Walks changes through a mode-aware six-phase workflow (HLD → LLD → EARS → intent-narrowing edge audit → tests-first → code) with mandatory stops between each phase. Bugs walk the arrow like any other change — no short-circuit. Enforces cascade…
testing-best-practices
Unit testing, integration testing, and test-driven development principles. Use when writing tests, reviewing test code, improving test coverage, or setting up testing strategy. Triggers on "write tests", "review tests", "testing best practices", or "TDD".
vibeguard-observe
Use when the user asks for a VibeGuard dashboard, hook health, stats, doctor output, metrics export, or local observability status from the Codex App plugin.