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-buildgit 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.00014 | $0.00159 |
| Opus 5 | $0.00007 | $0.00079 |
| Sonnet 5 | $0.00003 | $0.00032 |
| Haiku 4.5 | $0.00001 | $0.00016 |
Grade A, and why
af-build 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 3d 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 incremental-implementation skill and the test-driven-development skill via the skill tool.
Pick the next pending task from the plan. For each task:
- Read the task's acceptance criteria.
- Load relevant context: existing code, patterns, and types.
- Write a failing test for the expected behavior.
- Implement the minimum code to pass the test.
- Run the relevant test suite to check for regressions.
- Run the build to verify compilation.
- Mark the task complete and move to the next one.
If any step fails, invoke the debugging-and-error-recovery skill via the skill tool.
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.
- 3d ago First seen · 18 lines · 14 tokens per session scan A 780bbfb5158f
af-build is a command published in the GitHub repository chankov/agent-fleet (10 stars, last pushed 7d ago), licensed MIT. It adds 14 tokens to every session and 159 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.
tdd
强制执行测试驱动开发工作流。首先搭建接口，生成测试，然后从实现能通过测试的最小代码。确保 80%+ 的覆盖率。.