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 bravew/trove --skill trove-tddgit clone --depth 1 https://github.com/bravew/troveWrote 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/bravew/trove/trove-tdd)<a href="https://agentmods.dev/skills/bravew/trove/trove-tdd"><img src="https://agentmods.dev/badge/skills/bravew/trove/trove-tdd/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/bravew/trove/trove-tdd"><img src="https://agentmods.dev/badge/skills/bravew/trove/trove-tdd.svg" alt="Reviewed on agentmods" width="80" 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.00062 | $0.00424 |
| Opus 5 | $0.00031 | $0.00212 |
| Sonnet 5 | $0.00012 | $0.00085 |
| Haiku 4.5 | $0.00006 | $0.00042 |
Grade A, and why
trove-tdd 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 9d 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
Trove · v2026.7.4
Session Init
This skill ships Trove conventions. Prefer existing project patterns over generic best practices when they conflict.
trove-tdd
Write the test that fails for the right reason before you change the code. The test encodes intended behavior, not the current implementation.
Workflow
- Understand the intended behavior — what should be true that currently isn't.
- Choose the narrowest check that exercises it (unit over integration over E2E).
- Write a test that fails before the fix, for the reason you expect.
- Run it and confirm it fails on that reason — not a typo or a missing import.
- Make the smallest fix.
- Re-run; confirm it passes.
- Run nearby tests to catch fallout.
When to skip (escape hatch)
Prefer no new test over a bad test. Skip — and say why — when:
- The only path is a slow E2E flow or a broad harness with heavy setup.
- Reproducing it needs brittle mocks that would assert implementation detail, not behavior.
- The test target is genuinely unclear.
A bad test is one that passes when the bug is present, asserts on incidental implementation, or is so slow/flaky it gets disabled. Don't write it to look thorough.
Output
Report the evidence, not just the outcome: name the run that failed before the fix and the run that passed after (e.g. pnpm test reducer.test.ts red → green). If you skipped the test, state the reason in one line.
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.
- 9d ago First seen · 41 lines · 62 tokens per session scan A 582aee056938
trove-tdd is a skill published in the GitHub repository bravew/trove (10 stars, last pushed 10d ago), licensed MIT. It adds 62 tokens to every session and 424 once invoked, about $0.0003 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-31.
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.
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.
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.