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/design-and-deliver/claude-code-autoconfig/fleetgit clone --depth 1 https://github.com/design-and-deliver/claude-code-autoconfigWrote 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/design-and-deliver/claude-code-autoconfig/fleet)<a href="https://agentmods.dev/commands/design-and-deliver/claude-code-autoconfig/fleet"><img src="https://agentmods.dev/badge/commands/design-and-deliver/claude-code-autoconfig/fleet.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.00000 | $0.00737 |
| Opus 5 | $0.00000 | $0.00368 |
| Sonnet 5 | $0.00000 | $0.00147 |
| Haiku 4.5 | $0.00000 | $0.00074 |
Grade A, and why
fleet 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fleet
Several Claude sessions run against this repo at once. Some hold while others finish, and there is no single place that says who is doing what — so the state feels invisible even though every signal is already on disk. This joins them into one board.
READ-ONLY. It never merges, moves a branch, or writes to a worktree. Safe to run at any moment, including while everything is busy — which is exactly when you need it.
DEV-ONLY: gated out of user installs (DEV_ONLY_FILES in bin/cli.js), dogfooded from the CCA
repo like token-guard and whats-happening.
Step 1 — run the board
node "${CLAUDE_PROJECT_DIR:-.}/.claude/scripts/fleet.js"
If $ARGUMENTS contains all, append --all to include idle sessions.
Step 2 — report it
Print the script's output verbatim in a fenced block. It is already formatted as a board; re-narrating it row by row makes it longer and harder to scan than the raw output.
Then add at most two lines of interpretation, and only if there is a hazard block:
- SAME-TREE COLLISION — the one that loses work. Say which sessions should move to a worktree
(the newest, since they have the least invested), and that the fix is
EnterWorktree+node scripts/bootstrap-worktree.jsin those sessions. - DUPLICATE TITLE — say which session appears furthest along (most recent write) and that the others are candidates to stop.
- OVERLAP — name the branch to land first (the one the board already ordered first).
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.
- 5d ago First seen · 61 lines · 0 tokens per session scan A 123f252fec2d
fleet is a command published in the GitHub repository design-and-deliver/claude-code-autoconfig (2 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 737 tokens. 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.