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.
git clone --depth 1 https://github.com/craigcossairt/trellisWrote 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/commands/craigcossairt/trellis/tdd)<a href="https://agentmods.dev/commands/craigcossairt/trellis/tdd"><img src="https://agentmods.dev/badge/commands/craigcossairt/trellis/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/commands/craigcossairt/trellis/tdd"><img src="https://agentmods.dev/badge/commands/craigcossairt/trellis/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.00048 | $0.00166 |
| Opus 5.5 | $0.00019 | $0.00066 |
| Sonnet 5.5 | $0.00010 | $0.00033 |
| Haiku 4.5 | $0.00005 | $0.00017 |
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 20d 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
Follow the full methodology in docs/methodology/tdd.md - read it now if it isn't already in
context.
Non-negotiables (details and anti-patterns in the doc):
- ONE test at a time, vertical slices - never batch all tests then all code
- Agree the seams (public boundaries under test) with the user before writing any test
- Confirm red before implementing; confirm green before moving on; refactor only while green
- Expected values come from an independent source of truth, never recomputed the way the code does
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.
- 20d ago Changed · -1 lines 9667b12f3cbd
- 1mo ago First seen · 15 lines · 48 tokens per session scan A 3b41320becbe
tdd is a command published in the GitHub repository craigcossairt/trellis (5 stars, last pushed 13d ago), licensed MIT. It adds 48 tokens to every session and 166 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-08-31.
Other commands, from other repositories
implement
Execute tasks from a track's implementation plan following TDD workflow.
spec-impl
Execute spec tasks using TDD methodology.
api-aqa-flow
Workflow for backend API test automation: TMS / Issue Tracker test cases → automated API tests, HITL-gated.
implement
Execute all implementation tasks from tasks.md with test-driven development, parallel batching, and atomic commits.
tasks
Generate TDD task breakdown from plan.md with test-first sequencing and mockup-first mode (--ui-first).
test
A test-driven development workflow, or TDD, where tests describing the expected behavior are written before the implementation. For bugs, it first adds a test that reproduces the failure.