Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/stevengonsalvez/agents-in-a-boxnpx agentmods add skills/stevengonsalvez/agents-in-a-box/fleet-needsWrote 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/stevengonsalvez/agents-in-a-box/fleet-needs)<a href="https://agentmods.dev/skills/stevengonsalvez/agents-in-a-box/fleet-needs"><img src="https://agentmods.dev/badge/skills/stevengonsalvez/agents-in-a-box/fleet-needs/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/stevengonsalvez/agents-in-a-box/fleet-needs"><img src="https://agentmods.dev/badge/skills/stevengonsalvez/agents-in-a-box/fleet-needs.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.00112 | $0.02985 |
| Opus 5 | $0.00056 | $0.01492 |
| Sonnet 5 | $0.00022 | $0.00597 |
| Haiku 4.5 | $0.00011 | $0.00298 |
Grade B, and why
ainb-fleet:fleet-needs scanned grade B 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 11d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
> [`ainb fleet atc setup`](../atc/SKILL.md) (into `~/.claude/settings.json`). How it starts
The opening of the file, as written. The whole thing — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ainb fleet:fleet-needs — workflow-backed cockpit
The session "face" of the sensor-fusion hybrid. The deterministic brain is the
hangar workflow (verb=needs); this skill renders its output and handles the
irreducibly-interactive last mile (HUD + AskUserQuestion + routing).
fleet-needs vs needs — which skill?
This skill (
fleet-needs) is the workflow-backed "Jarvis" cockpit. It runs the deterministichangarworkflow (verb=needs) for the batched discover→enrich→prioritize chain, and adds key-route ASK answering (presses the target's picker keys via tmux for an already-open AskUserQuestion). It requires the workflow gateCLAUDE_CODE_WORKFLOWS=1.
/ainb-fleet:needsis the plain control panel — prompt-driven, no gate, works everywhere. It is the canonical fallback: if the gate is off, this skill stops and hands off toneeds(see Step 0).Both read the same underlying
ainb fleet needsdata — same panel content, same materializedcurrent_statesource (below). The difference is purely the machinery: workflow-batched cockpit (here) vs plain prompt panel (needs).
SESSION (this skill) ──Workflow({name:'ainb-fleet:jarvis', args:{verb:'needs'}})──▶ brain
render HUD ◀──{banner,cards,asks}──────────────────────────────────────────┘
AskUserQuestion per ask ──answer──▶ tmux send-keys (write leg)
Read/write split — architectural principle
| Direction | Channel | Why |
|---|---|---|
| Reads | materialized current_state (hooks → events.jsonl → notifyd → SQLite) FIRST; live tmux pane + JSONL transcript scan as the fallback for non-Claude agents (Codex/Gemini) and un-materialized sessions |
event-sourced latest stage; replayable; ground truth |
| Writes | tmux send-keys — direct keystrokes to the target pane (verify with capture-pane) | deterministic, no broker latency or delivery gap |
| Fallback writes | peers/broker via ainb fleet broadcast |
only when no tmux_session known; broker has a known delivery gap |
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.
- 11d ago First seen · 262 lines · 112 tokens per session scan B 9f6d1dd5d626
ainb-fleet:fleet-needs is a skill published in the GitHub repository stevengonsalvez/agents-in-a-box (23 stars, last pushed today), licensed MIT. It adds 112 tokens to every session and 2,985 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
saga-orchestration
Implement saga patterns for distributed transactions and cross-aggregate workflows. Use this skill when implementing distributed transactions across microservices where 2PC is unavailable, designing compensating actions for failed order workflows that span inventory, payment, and shipping services, building…
task-coordination-strategies
Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
context-driven-development
Creates and maintains project context artifacts (product.md, tech-stack.md, workflow.md, tracks.md) in a conductor/ directory. Scaffolds new projects from scratch, extracts context from existing codebases, validates artifact consistency before implementation, and synchronizes documents as the project evolves. Use when…