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 skills/asheshgoplani/agent-deck/fleetnpx skills add asheshgoplani/agent-deck --skill fleetgit clone --depth 1 https://github.com/asheshgoplani/agent-deckWhat 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.00094 | $0.03922 |
| Opus 5 | $0.00047 | $0.01961 |
| Sonnet 5 | $0.00019 | $0.00784 |
| Haiku 4.5 | $0.00009 | $0.00392 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fleet
Fan out several independent agent-deck child sessions from inside your current session, keep working, and check their progress on demand — without blocking and without consuming any delivery events.
Requires: the agent-deck session children and launch --assert-done
features. If agent-deck session children --help succeeds, you have them.
When to use
Use this when the user wants more than one agent working at once and wants to supervise from the parent session — e.g. "launch 5 sessions to each tackle a file", "fan out these tasks", "spin up a fleet and tell me when they're done".
This differs from the single sub-agent pattern in the agent-deck skill (one
child + fire-&-forget / on-demand / blocking retrieval). Fleet is many
children + a non-blocking peek across all of them.
Run from inside an agent-deck session. Launching auto-parents each child to the launching session, which is what makes them show up nested in the TUI and routes their completion back to you. (If you are not in a session, the children still launch but won't be grouped under a parent.)
Need a specific parent? Auto-parenting picks the launching session. To
parent a child to a different session — e.g. fanning out under a named conductor,
or launching from outside that session — pass --parent <session-id-or-title>.
Spell out the long form: never use the short -p to set a parent (see the
-p pitfall in Notes).
Before you fan out
- Check for shared singletons. N sessions on the same project can't truly run in parallel if they serialize on one resource — a single dev DB, a bound port, one dev-server lock file. If they'd share one, either give each child isolated resources (own DB name + port) or run one coherent session instead of a fleet.
- Worktree children need deps installed first. A freshly created git worktree
has no
node_modules/ vendored deps. Make the first instruction in the child's-mprompt install them — and for a locked monorepo, install from the frozen lockfile, never regenerate it (e.g.pnpm install --frozen-lockfile). Otherwise the child's first test/build/e2e fails confusingly. - Long prompts: pass via a file. For a big multi-line task, write it to a
file and pass
--message-file task.md(or--message-file -to read stdin) instead of-m. The file is read directly by agent-deck, so backticks,$, and quotes never round-trip through the shell. Also works onsession startandsession send(there it replaces the positional message). On older builds without the flag, fall back to-m "$(cat task.md)".
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 · 304 lines · 94 tokens per session scan A 5a32bd42d94d
fleet is a skill published in the GitHub repository asheshgoplani/agent-deck (828 stars, last pushed yesterday), licensed MIT. It adds 94 tokens to every session and 3,922 once invoked, about $0.0005 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-30.
Other skills, from other repositories
rosetta
Reconcile ALL prior agent conversations (Claude Code, Codex, Droid/Factory, Hermes, Cursor) with git history and docs into a cited ground truth, and distill durable decision records (ADRs/PDRs/BDRs). Use whenever the user wants to catch up on or get the state of a project, build or refresh a ground truth, read or mine…
microverse
Microverse convergence loop — optimize a metric through targeted, incremental changes.
portal-gun
Cross-repo pattern extraction and transplant PRD generation.
council-of-ricks
PR branch stack review with directive generation.
meeseeks
Rotating-focus code review with commit-on-finding.
pickle-refine-prd
Refine and decompose a PRD into atomic tickets using parallel analysis.