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/chankov/agent-fleet/af-testgit clone --depth 1 https://github.com/chankov/agent-fleetWhat 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.00013 | $0.00155 |
| Opus 5 | $0.00006 | $0.00077 |
| Sonnet 5 | $0.00003 | $0.00031 |
| Haiku 4.5 | $0.00001 | $0.00015 |
Grade A, and why
af-test 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
Invoke the test-driven-development skill via the skill tool.
For new features:
- Write tests that describe the expected behavior and confirm they fail.
- Implement the code to make them pass.
- Refactor while keeping tests green.
For bug fixes, use the Prove-It pattern:
- Write a test that reproduces the bug and must fail.
- Confirm the test fails.
- Implement the fix.
- Confirm the test passes.
- Run the relevant full test suite for regressions.
For browser-related issues, also invoke browser-testing-with-devtools via the skill tool to verify with Chrome DevTools MCP.
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 · 22 lines · 13 tokens per session scan A 06a71d961a35
af-test is a command published in the GitHub repository chankov/agent-fleet (10 stars, last pushed 7d ago), licensed MIT. It adds 13 tokens to every session and 155 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-31.
Other commands, from other repositories
tdd-requirements
TDD開発の要件整理を行います。機能要件を明確化し、テスト駆動開発のための準備を行います。.
go-test
Go TDD workflow with table-driven tests.
pm-auto-design2dev
設計レビューから実装完了まで完全自動化（設計レビュー→作業計画→TDD実装）.
task-verify
PitWay: Run an inprogress task's approved verification command and persist evidence.
execute-plan
Execute an implementation plan methodically with TDD and continuous validation.
eval
Evaluate and improve one healthcare agent's system prompt. Run up to 5 iterations of: prepare fixed questions -> answer -> judge -> improve -> re-score -> commit if better.