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/sam-agents/samWrote 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/sam-agents/sam/build-tdd)<a href="https://agentmods.dev/commands/sam-agents/sam/build-tdd"><img src="https://agentmods.dev/badge/commands/sam-agents/sam/build-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/sam-agents/sam/build-tdd"><img src="https://agentmods.dev/badge/commands/sam-agents/sam/build-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.00035 | $0.00078 |
| Opus 5.5 | $0.00014 | $0.00031 |
| Sonnet 5.5 | $0.00007 | $0.00016 |
| Haiku 4.5 | $0.00003 | $0.00008 |
Grade A, and why
build-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 1mo 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
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_sam/core/workflows/build-tdd/workflow.md, READ its entire contents and follow its directions exactly!
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.
- 1mo ago First seen · 7 lines · 35 tokens per session scan A 04d761e75905
build-tdd is a command published in the GitHub repository sam-agents/sam (19 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 78 once invoked, about $0.0001 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-30.
Other commands, from other repositories
implement
E2E-first Test driven development — unit tests written last.
examples
Real-world examples and scenarios for pair programming sessions.
start
Start a new pair programming session with AI assistance.
workflow-implement
Exécuter la phase d'Implémentation - développement sprint avec TDD/BDD.
fix
Correction automatisee des bugs identifies par la QA Recette.
tdd
A command for test-driven development, a method where you write a failing test first, then code to pass it, and finally improve the code.