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/dixus/claudeframework/fleetnpx skills add dixus/claudeframework --skill fleetgit clone --depth 1 https://github.com/dixus/claudeframeworkWhat 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.00037 | $0.03368 |
| Opus 5 | $0.00018 | $0.01684 |
| Sonnet 5 | $0.00007 | $0.00674 |
| Haiku 4.5 | $0.00004 | $0.00337 |
Grade B, and why
fleet 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 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
3. If no name provided, find the most recently modified `decomposition-*.md` in `.claude/specs/` How it starts
The opening of the file, as written. The whole thing — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrate parallel /ship runs for decomposed PRDs. Analyze file conflicts across features, group non-conflicting features into parallel batches, execute each in an isolated git worktree, and merge results back to main conflict-free.
$ARGUMENTS is optional:
- First positional arg: decomposition name (matches
.claude/specs/decomposition-<name>.md) --dry-run— generate specs and show batch plan, but don't implement--max-parallel N— limit concurrent worktrees (default: 5)--batch-only— run batch 1 only, then stop for review
Architecture
Fleet is a thin orchestrator — it never reads code files or accumulates implementation context. It reads manifests, spec metadata, and delegates all per-feature work to /ship subagents running in isolated worktrees.
Fleet orchestrator (this skill)
├── Step 0: load decomposition manifest
├── Step 1: collect file claims from specs
├── Step 2: conflict analysis → batch plan
├── Step 3: execution plan + user approval
├── Step 4: batch execution loop
│ ├── Launch /ship agents in isolated worktrees (background)
│ ├── Wait for completion
│ ├── Merge completed branches to main
│ └── Advance to next batch
├── Step 5: final integration verify
├── Step 6: failure triage
└── Step 7: fleet report + metrics
Step 0 — Load decomposition manifest
- Parse
$ARGUMENTSfor the decomposition name and flags (--dry-run,--max-parallel N,--batch-only) - If a decomposition name is provided, read
.claude/specs/decomposition-<name>.md - If no name provided, find the most recently modified
decomposition-*.mdin.claude/specs/ - If no decomposition manifest exists: stop — "No decomposition found. Run
/decomposefirst to break your concept into PRDs." - Parse the manifest's features table: extract feature name, PRD path, dependencies, status
- Filter to features with status
pendingonly (skipcompleted,in-progress,skipped) - If no pending features: "All features are already completed or in-progress."
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 · 330 lines · 37 tokens per session scan B 70840e5689e6
fleet is a skill published in the GitHub repository dixus/claudeframework (10 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 3,368 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.