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 agentmods add commands/dshakes/compass/tddgit clone --depth 1 https://github.com/dshakes/compassWhat 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 | $0.00012 | $0.00204 |
| Opus 5 | $0.00006 | $0.00102 |
| Sonnet 5 | $0.00002 | $0.00041 |
| Haiku 4.5 | $0.00001 | $0.00020 |
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 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.
What it actually says
Implement the following using strict TDD: $ARGUMENTS
- Red — Write the smallest test that captures the desired behavior and fails for the right reason. Run it; show me the failure. Do not write implementation yet.
- Green — Write the minimum code to make that test pass. Run it; show it pass.
- Refactor — Clean up while keeping the test green. Re-run.
- Repeat for each behavior/edge case until the requirement is fully covered.
Match the repo's existing test framework and style. Cover error paths, not just the happy path. Use the test-runner subagent to execute suites so we stay cheap. Report the final test list and results.
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 First seen · 18 lines · 12 tokens per session scan A dc28f3dbad73
tdd is a command published in the GitHub repository dshakes/compass (19 stars, last pushed 8d ago), licensed MIT. It adds 12 tokens to every session and 204 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-08-30.
Other commands, from other repositories
tdd-requirements
TDD開発の要件整理を行います。機能要件を明確化し、テスト駆動開発のための準備を行います。.
go-test
Go TDD workflow with table-driven tests.
pm-auto-design2dev
設計レビューから実装完了まで完全自動化（設計レビュー→作業計画→TDD実装）.
feature-plan
Analyzes feature specifications and creates detailed TDD implementation plans with incremental PR breakdown and specialist agent assignments. Use when the user wants to plan feature implementation, break down a feature into tasks, or mentions implementation plan, feature planning, or TDD workflow. WHEN NOT: Writing…
ralph.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
task-verify
PitWay: Run an inprogress task's approved verification command and persist evidence.