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/arnaldo-delisio/claude-code-studio/test-firstgit clone --depth 1 https://github.com/arnaldo-delisio/claude-code-studioWrote 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/arnaldo-delisio/claude-code-studio/test-first)<a href="https://agentmods.dev/commands/arnaldo-delisio/claude-code-studio/test-first"><img src="https://agentmods.dev/badge/commands/arnaldo-delisio/claude-code-studio/test-first.svg" alt="Measured on agentmods" 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 | $0.00011 | $0.00035 |
| Opus 5 | $0.00005 | $0.00017 |
| Sonnet 5 | $0.00002 | $0.00007 |
| Haiku 4.5 | $0.00001 | $0.00003 |
Grade A, and why
test-first 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 4d 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
Write tests before implementation following the red-green-refactor cycle.
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.
- 4d ago First seen · 6 lines · 11 tokens per session scan A c9828a1f6f4b
test-first is a command published in the GitHub repository arnaldo-delisio/claude-code-studio (276 stars, last pushed 1y ago), licensed MIT. It adds 11 tokens to every session and 35 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-refactor
TDDのRefactorフェーズを実行します。テストを通す実装が完了した後、コード品質の改善とリファクタリングを行います。.
tdd-requirements
TDD開発の要件整理を行います。機能要件を明確化し、テスト駆動開発のための準備を行います。.
spec-impl
Execute spec tasks using TDD methodology.
task-verify
PitWay: Run an inprogress task's approved verification command and persist evidence.
verification-repair
PitWay: Bounded, approve-before-edit correction after every task is done.
task-discard
PitWay: Abandon a dispatched task's worktree without integrating.