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/chankov/agent-fleetWrote 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/chankov/agent-fleet/af-build)<a href="https://agentmods.dev/commands/chankov/agent-fleet/af-build"><img src="https://agentmods.dev/badge/commands/chankov/agent-fleet/af-build/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/chankov/agent-fleet/af-build"><img src="https://agentmods.dev/badge/commands/chankov/agent-fleet/af-build.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.00014 | $0.00159 |
| Opus 5.5 | $0.00006 | $0.00064 |
| Sonnet 5.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 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.
This is a copy
75% identical to build — 48 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 1mo 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 (19 stars, last pushed 4d ago), licensed MIT. It adds 14 tokens to every session and 159 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 75% identical to build, differing in 48 lines, and is treated as a copy.
Other commands, from other repositories
bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
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.
usage-add
PitWay: Accumulate measured planning or qa token usage onto a milestone.
speckit.tdd.plan
Derive the feature's test list by delegating to zfa tdd plan (deterministic engine); falls back to LLM-guided derivation only when zfa is unavailable.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
tdd
Canon TDD (specify, encode, fulfill) with one test at a time, approval gates, and kitchen-cleaning refactor when needed.