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-test)<a href="https://agentmods.dev/commands/chankov/agent-fleet/af-test"><img src="https://agentmods.dev/badge/commands/chankov/agent-fleet/af-test/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-test"><img src="https://agentmods.dev/badge/commands/chankov/agent-fleet/af-test.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.00013 | $0.00155 |
| Opus 5.5 | $0.00005 | $0.00062 |
| Sonnet 5.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 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.
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.
- 1mo 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 (19 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 155 once invoked, about $0.0001 per session on Opus 5.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
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.
dashboard
Generar dashboard HTML local con métricas de eficiencia del proyecto SDD.
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.