Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add pwdev-solucoes/pwdev-claude-marketplace/plugin install pwdev-codeWrote 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/commands/pwdev-solucoes/pwdev-claude-marketplace/fleet)<a href="https://agentmods.dev/commands/pwdev-solucoes/pwdev-claude-marketplace/fleet"><img src="https://agentmods.dev/badge/commands/pwdev-solucoes/pwdev-claude-marketplace/fleet.svg" alt="Measured on agentmods" 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.00035 | $0.01831 |
| Opus 5 | $0.00017 | $0.00915 |
| Sonnet 5 | $0.00007 | $0.00366 |
| Haiku 4.5 | $0.00003 | $0.00183 |
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 8d 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pwdev-code:fleet — Parallel Phase Fleet (worktree + tmux + docker)
Role (orchestrator — you dispatch the fleet, you never implement)
You spin up, monitor, and tear down a small fleet (max fleet.max_concurrent,
default 3) of fully isolated, unattended pipelines — one per phase-slug. Each
pipeline runs plan → execute → review → verify end-to-end in its own git
worktree, its own docker-compose stack on its own ports, and its own real
claude process inside a tmux window. You yourself only shell out to the
fleet scripts and report status — the actual work happens in scripts and in
the spawned claude processes, not in your context.
This command does not run discover or design — every target phase-slug
must already have spec.md + decisions.md (i.e. /pwdev-code:design was
already run and approved by a human). simplify is also excluded from the
default pipeline (its APPLY step needs per-ID human approval, which is not
available headless).
⚠️ Read before using
- Each pipeline runs
claude -pheadless, withfleet.permission_mode(defaultbypassPermissions) — it accepts edits and runs Bash without asking. This is only acceptable because it runs inside an isolated git worktree (never your main working tree) and an isolated docker-compose stack (never your main environment). It never pushes, never merges to your current branch, and never removes a worktree on its own. - Any place the underlying commands (
plan,execute,review,verify) would normally pause for human approval, the headless session is instructed to proceed automatically instead. That means plans and fixes in a fleet run are not human-reviewed until you look at the diff — review it before you merge. - Merging a fleet branch back into your current branch (
--teardown --merge) is a separate, explicit step you run yourself.
Input
$ARGUMENTS:
<phase-slug> [phase-slug...](1 tofleet.max_concurrentslugs) → start a fleet--status→ print the current fleet table once (no tmux needed)--teardown <slug> [--merge]→ stop and clean up one fleet member--teardown --all [--merge]→ teardown every active fleet member
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.
- 8d ago First seen · 157 lines · 35 tokens per session scan A d0d4f13645d6
fleet is a command published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 35 tokens to every session and 1,831 once invoked, about $0.0002 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-31.
Other commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
handoff
Export a Waybill Bundle by default, or import one when requested.