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 hon454/grimoire --skill tddgit clone --depth 1 https://github.com/hon454/grimoireWrote 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/hon454/grimoire/tdd)<a href="https://agentmods.dev/skills/hon454/grimoire/tdd"><img src="https://agentmods.dev/badge/skills/hon454/grimoire/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/hon454/grimoire/tdd"><img src="https://agentmods.dev/badge/skills/hon454/grimoire/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.00052 | $0.02041 |
| Opus 5.5 | $0.00021 | $0.00816 |
| Sonnet 5.5 | $0.00010 | $0.00408 |
| Haiku 4.5 | $0.00005 | $0.00204 |
Grade A, and why
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 26d 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test-driven development
Write the test first. Watch it fail. Write the minimal code that makes it pass. Clean up. Repeat.
Core principle: if you did not watch the test fail, you do not know that it tests the right thing.
When this applies
Always: new features, bug fixes, refactors, behaviour changes.
Exceptions, only with the user's agreement: throwaway prototypes, generated code, configuration files.
Thinking "skip TDD just this once"? That is a rationalization. See the table below.
The iron law
NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST
Wrote code before the test? Delete it and start over from the test. Do not keep it "as reference", do not adapt it while writing tests, do not look at it. Implement fresh from the tests.
Before the loop: agree the seams
A seam is the public boundary you test at: the interface where behaviour is observable without reaching inside. Tests live at seams, never against internals.
Before the first test, write down which seams you will test and confirm them with the user when the interface is new or unclear. Give each proposed seam one line on what it catches and what it misses. Testing effort then lands on critical paths and real logic instead of every edge of every private function.
If the shape of the interface is itself in question, settle that first: a module that is hard to test is hard to use.
The loop: red, green, refactor
Work in vertical slices: one test, one minimal implementation, then the next test. Do not write all tests first and then all code. Bulk tests verify imagined behaviour and commit you to a structure before you understand the implementation. Each test is a tracer bullet that responds to what the last cycle taught you.
RED: write one failing test
One behaviour, a clear name that states the behaviour, real code rather than mocks wherever possible.
// Good: clear name, exercises real code, one behaviour
test('retries a failing operation up to 3 times', async () => {
let attempts = 0;
const operation = () => {
attempts++;
if (attempts < 3) throw new Error('fail');
return 'success';
};
const result = await retryOperation(operation);
expect(result).toBe('success');
expect(attempts).toBe(3);
});
// Bad: vague name, asserts on the mock instead of the code
test('retry works', async () => {
const mock = jest.fn().mockRejectedValueOnce(new Error()).mockRejectedValueOnce(new Error()).mockResolvedValueOnce('ok');
await retryOperation(mock);
expect(mock).toHaveBeenCalledTimes(3);
});
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.
- 26d ago First seen · 186 lines · 52 tokens per session scan A a609b9762165
tdd is a skill published in the GitHub repository hon454/grimoire (0 stars, last pushed 25d ago), licensed MIT. It adds 52 tokens to every session and 2,041 once invoked, about $0.0002 per session on Opus 5.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-10-21.
tdd compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| tddhon454/grimoire | Skill | 0 | 25d ago | MIT | A | 52 | Claude Code, Codex |
| engram-testing-coverageGentleman-Programming/engram | Skill | 8.2k | 2d ago | MIT | A | 25 | Claude Code, Codex |
| principle-test-behavior-not-implementationmichael-denyer/pstack-claude | Skill | 4.4k | 2d ago | MIT | A | 50 | Claude Code |
| nw-ddd-eventsourcingnWave-ai/nWave | Skill | 635 | yesterday | MIT | A | 38 | Claude Code |
| nw-fp-clojurenWave-ai/nWave | Skill | 635 | yesterday | MIT | A | 25 | Claude Code |
| nw-leanux-methodologynWave-ai/nWave | Skill | 635 | yesterday | MIT | A | 37 | Claude Code |
| tddcodewithmukesh/dotnet-claude-kit | Skill | 836 | 11d ago | MIT | A | 81 | Claude Code |