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 bostonaholic/team --skill test-driven-bug-fixgit clone --depth 1 https://github.com/bostonaholic/teamWrote 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/bostonaholic/team/test-driven-bug-fix)<a href="https://agentmods.dev/skills/bostonaholic/team/test-driven-bug-fix"><img src="https://agentmods.dev/badge/skills/bostonaholic/team/test-driven-bug-fix.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.00026 | $0.00505 |
| Opus 5 | $0.00013 | $0.00253 |
| Sonnet 5 | $0.00005 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
test-driven-bug-fix 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 2d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test-Driven Bug Fix
Prove each bug and pin its behavior before changing production code. Read references/procedure.md for detailed checks, examples, and commit templates.
Triage
Classify first:
- Product: continue below.
- Test impl: fix the test separately; never change production for a bad test.
- Infra: fix the environment, not product behavior.
- Tooling: fix the runner or build system.
Intermittency is not a fifth bucket. Call the Skill tool with systematic-debugging to reproduce it
and its Root Cause Analysis (5 Whys) for non-obvious causes.
Step 1: Reproduce
Before any code change, reliably reproduce the failure. Record exact inputs, actual and expected behavior, and affected files/functions. Observe; do not hypothesize a fix.
Step 2: Write a Failing Test
Write a test that:
- Reproduces the bug with the exact scenario.
- asserts correct behavior, not current behavior;
- fails through the intended assertion, not infrastructure;
- names the behavior, not a bug number or method.
Run it and the existing suite. The new test must fail for the right reason and all prior tests must pass. Do not continue without this Red state.
Step 3: Fix Minimally
Change only code causing the defect. Do not refactor, extend scope, alter the test, or fix adjacent bugs. Run tests after each change. Green means the new and existing tests pass.
Step 4: Verify
- Run the full suite; undo and investigate any regression.
- Re-run the original inputs.
- Search for related instances and file them separately.
- Mutation-check the regression test: temporarily revert one fix line and require the new test to fail. Restore it. If it stays green, strengthen the assertion or reproduction.
Commits
Keep two atomic commits:
test: reproduce <bug description> with failing test
fix: <minimal description of the fix>
The fix targets the root cause (principle-fix-root-causes). It is not a
refactor, feature, or workaround.
What ships with it
2 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.
- 2d ago Changed · -82 lines · -19 tokens per session 3fced1afea25
- 3d ago First seen · 151 lines · 45 tokens per session scan A cacaeeca4390
test-driven-bug-fix is a skill published in the GitHub repository bostonaholic/team (11 stars, last pushed 2d ago), licensed MIT. It adds 26 tokens to every session and 505 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
behavior-contract
Bug condition/postcondition formalization as testable Behavior Contracts. Defines invariants that must be preserved across fixes.
quality-hooks
Language-specific auto-lint/format/typecheck pipeline. Supports Python (ruff+pyright), TypeScript (prettier+eslint+tsc), Go (gofmt+golangci-lint). Auto-fix and convergence loops.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
test-driven-development
Strict RED-GREEN-REFACTOR cycle enforcement. Tests are never skipped or deferred. Run mode only, never watch mode. Exit code evidence mandatory.
tdd-enforcement
Red-Green-Refactor TDD methodology with mandatory failing tests, minimal implementation, quality refactoring, and 80% coverage gating.
orchestrated-execution
Execute work units through the rigorous 4-phase Metaswarm cycle (Implement -> Validate -> Adversarial Review -> Commit) with independent quality gate enforcement.