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 skills add bradlay/claude-code-recipes --skill fleet-setupgit clone --depth 1 https://github.com/bradlay/claude-code-recipesWrote 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/skills/bradlay/claude-code-recipes/fleet-setup)<a href="https://agentmods.dev/skills/bradlay/claude-code-recipes/fleet-setup"><img src="https://agentmods.dev/badge/skills/bradlay/claude-code-recipes/fleet-setup/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/skills/bradlay/claude-code-recipes/fleet-setup"><img src="https://agentmods.dev/badge/skills/bradlay/claude-code-recipes/fleet-setup.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.00094 | $0.01846 |
| Opus 5.5 | $0.00038 | $0.00738 |
| Sonnet 5.5 | $0.00019 | $0.00369 |
| Haiku 4.5 | $0.00009 | $0.00185 |
Grade A, and why
fleet-setup 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 13d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fleet Setup
This skill is the single source of truth for the fleet structure contract. fleet-lead and fleet-sweep cite it rather than repeating its values, so the three cannot drift apart. When any of the three changes, review all three together.
The contract is runtime-neutral. The mechanics of a particular runtime live in adapter references:
- references/herdr.md: sessions as panes and tabs in the Herdr terminal multiplexer (Claude Code or Codex sessions).
- references/claude-code.md: Claude Code features the fleet relies on (Monitor, scheduled prompts, goals, hooks), including an optional hook pattern for enforcing role boundaries.
- references/codex.md: a Codex native task tree, with a table mapping fleet operations to collaboration tools.
- references/operator-surface.md: operator invariant 6, the decision option format, the operator goal, explicit model ids, and role-scoped launch flags.
If the chosen runtime cannot keep the four roles separate, report that as unsupported. Never merge roles silently to make the fleet fit.
The structure contract
Four tiers. Workers never share the coordinators' control surface.
| Tier | Name | Model | Placement | Role in one line |
|---|---|---|---|---|
| operator | fleet-operator |
<fast-model> |
control surface, top, full width | Sole interactive channel to the human; relays directives to the leader and answers back |
| leader | fleet-lead-<n> |
<coordinator-model> |
control surface, bottom left | Coordinator: rulings, gates, go decisions, succession |
| dispatcher | fleet-dispatcher-<n> |
<fast-model> |
control surface, bottom right | Relay and execution lane: spawns and briefs workers, runs commit, push and deploy commands on gated work |
| worker | descriptive unique name | leader's choice by task | own tab or own session, never the control surface | Authors code, plans, docs, tests |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 13d ago Changed · +5 lines dcab8f7fd4ac
- 18d ago First seen · 143 lines · 94 tokens per session scan A 446f1444dfba
fleet-setup is a skill published in the GitHub repository bradlay/claude-code-recipes (2 stars, last pushed 4d ago), licensed MIT. It adds 94 tokens to every session and 1,846 once invoked, about $0.0004 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-10-17.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…