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 skills add pwdev-solucoes/pwdev-claude-marketplace --skill flow-fleetgit clone --depth 1 https://github.com/pwdev-solucoes/pwdev-claude-marketplaceWrote 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/pwdev-solucoes/pwdev-claude-marketplace/flow-fleet)<a href="https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/flow-fleet"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/flow-fleet/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/pwdev-solucoes/pwdev-claude-marketplace/flow-fleet"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/flow-fleet.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.00059 | $0.00910 |
| Opus 5 | $0.00030 | $0.00455 |
| Sonnet 5 | $0.00012 | $0.00182 |
| Haiku 4.5 | $0.00006 | $0.00091 |
Grade A, and why
flow-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 6d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operate a Flow Fleet
Read fleet, safety, artifacts, and collaboration before acting.
Route
Interpret only these routes:
<slugs>: launch one or more approved lowercase phase slugs.--status: invoke packagedfleet-dashboard.sh --once.--teardown <slug>: invoke packagedfleet-teardown.sh <slug>and preserve its branch and worktree.--teardown --all: enumerate validated.planning/flow/fleet/<slug>.jsonentries and invoke packaged teardown once per slug.
Pass --merge to teardown only when the user explicitly requests it. Never merge a non-DONE member or translate state into legacy paths.
Launch
-
Inspect repository status, confirm a named current branch, inspect
.planning/flow/config.json, and inspect the requested approvedspec.mdanddecisions.mdcontracts. Never read.env.fleet. -
Resolve scripts from this installed skill at
../../scripts/; call only packaged fleet and audit scripts for lifecycle operations. -
Use the launcher of the runtime you are running as, and never the other one. The runtime is fixed by that choice, is recorded in the central member, and is refused by a runner bound to a different one. Before the first launch, display the exact autonomous command shape of that runtime:
Codex —
fleet-up.sh:codex exec --dangerously-bypass-approvals-and-sandbox --ephemeral --cd <worktree> --output-schema <fleet-result-schema> --output-last-message <result-file> <autonomous-prompt>Claude —
claude-fleet-up.sh:claude -p --dangerously-skip-permissions --no-session-persistence --output-format json <autonomous-prompt> -
Require explicit acknowledgement of the dangerous flag of that runtime —
--dangerously-bypass-approvals-and-sandboxfor Codex,--dangerously-skip-permissionsfor Claude. Do not persist a missing fleet block or launch a member before acknowledgement. Reject a configuredpermission_modeother thandanger-full-access. -
After acknowledgement, require the configuration root and any existing
.fleetvalue to be objects. Reject an existingpermission_modeunless it is exactlydanger-full-access; require the exact JSON booleanauto_simplify: falseand exact packaged Compose filename before launch. -
Merge the exact defaults from fleet into both absent and partial fleet blocks with
jq: set.fleet = ($fleet_defaults * (.fleet // {})). Write through a same-directory temporary file and atomically rename it only after validation. This defaults-first recursive merge fills missing known fields while every existing known or unknown field wins; never overwrite permission mode to dangerous. -
For multiple slugs, compare their specification and decision text for repeated repository paths. Emit an advisory overlap warning with the matching paths; let the human decide and never block automatically.
-
Invoke the packaged launcher of your runtime once per acknowledged slug —
fleet-up.sh <slug>as Codex,claude-fleet-up.sh <slug>as Claude. Either one binds exact contract hashes and initiating branch/base identity, records the runtime, and rejects unsafe symlinked state paths. Both route their tmux pane to the same autonomous runner, which owns locks, process-group ownership, structured result validation, per-stage commits, and the two-cycle correction cap. Stop launching further members after any failure and report the recovery state.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 48 lines · 59 tokens per session scan A f1eca8a82708
flow-fleet is a skill published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 59 tokens to every session and 910 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
github-notification-triage
Triage GitHub notifications and issue/PR queues.