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/lacion/fleet-deck/fleetgit clone --depth 1 https://github.com/lacion/fleet-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.00018 | $0.00643 |
| Opus 5 | $0.00009 | $0.00321 |
| Sonnet 5 | $0.00004 | $0.00129 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade A, and why
fleet scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: Bash(curl:*), Bash(cat:*) How it starts
The opening of the file, as written. The whole thing — 27 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fleet endpoint and state (raw)
!PORT=${FLEETDECK_PORT:-4711}; case "$PORT" in ''|*[!0-9]*|??????*) PORT=4711;; *) if [ "$PORT" -lt 1 ] || [ "$PORT" -gt 65535 ]; then PORT=4711; fi;; esac; printf 'FLEET_BOARD_URL=http://127.0.0.1:%s/\n' "$PORT"; TOKEN=$(cat "${FLEETDECK_HOME:-$HOME/.fleetdeck}/token" 2>/dev/null); curl -sf -m 2 ${TOKEN:+-H "Authorization: Bearer $TOKEN"} "http://127.0.0.1:$PORT/state" || echo FLEET_DAEMON_DOWN
Your task
Report on the fleet using ONLY the endpoint and raw state above. The first line is the exact board URL for this environment; use its value verbatim. Print exactly this, nothing more:
If the raw state is FLEET_DAEMON_DOWN (or empty / not JSON):
Board: fleet daemon not running — it starts with your next session
Otherwise a compact summary (aim for under 15 lines):
Board: <the FLEET_BOARD_URL value above>- Sessions grouped by column, in this order: needsyou, working, verifying, queued, idle, offline. One line per column that has sessions:
working (2): NOVA — fleetdeck (main) · editing derive.mjs, ...using each session'scallsign,repo_name,branch, andnote/taskwhen present. Skip empty columns; summarize offline as a count only (e.g.offline: 3). - Conflicts: if
conflictsis non-empty, one line per conflict:⚠ <rel_path> — <severity> — sessions: <callsigns or ids>. Otherwiseconflicts: none. - Mail:
mail_pendingis a per-session count map{<session_id>: <count>}(sessions with no queued mail appear with 0). Compute N as the total across all sessions — thesumof every value in the map. If N > 0:mail: N queued —followed by a per-route breakdown derived frommail_meta(only list routes that have queued mail):watcher= wakes immediately,pane= typed into the pane after a grace window,turn-boundary= delivered at the next turn boundary,offline-queued= held until the session is resumed. Example:mail: 3 queued — 1 wakes immediately (watcher), 1 typed into pane, 1 held until resume (offline). Otherwise omit the line.
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.
- 2d ago First seen · 27 lines · 18 tokens per session scan A 22417b737e23
fleet is a command published in the GitHub repository lacion/fleet-deck (28 stars, last pushed 4d ago), licensed MIT. It adds 18 tokens to every session and 643 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
lean-commit
Tier-A lean commit — only your paths, no changelog.d/push in same turn.
template
Manage issue templates for streamlined issue creation.
design-review
Workflow recipe — review a design end-to-end, ending in measured numbers rather than adjectives, by chaining 4 skills.
setup-pm-skills
Onboard a new user — find out what they do, recommend the right bundles & top skills, and set up a project CONTEXT.md so every skill is tailored to them.
autobot-result
Print the most recent result.md for an autobot session, so the user can see how a bot is doing without attaching to its tmux session.
ci-report
Generate a CI failure report for PR $PRNUMORURL (or current branch if no argument given).