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-compatgit 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-compat)<a href="https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/flow-compat"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/flow-compat/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-compat"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/flow-compat.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.00052 | $0.00673 |
| Opus 5 | $0.00026 | $0.00336 |
| Sonnet 5 | $0.00010 | $0.00135 |
| Haiku 4.5 | $0.00005 | $0.00067 |
Grade A, and why
flow-compat 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Route PWDEV Code Intent to PWDEV Flow
Read migration before routing legacy initialization or project adoption. Read fleet and delegation before routing their respective operational commands.
Supported routing
| Legacy intent | Canonical skill |
|---|---|
init, session |
$flow-init |
quick |
$flow-quick |
discover |
$flow-discover |
design |
$flow-design |
plan |
$flow-plan |
execute |
$flow-execute |
review |
$flow-review |
verify |
$flow-verify |
product |
$flow-product |
memory |
$flow-memory |
simplify |
$flow-simplify |
health |
$flow-health |
maintenance |
$flow-maintenance |
audit |
$flow-audit |
fleet |
$flow-fleet |
delegate |
$flow-delegate auto |
codex |
$flow-delegate with explicit provider codex |
opencode |
$flow-delegate with explicit provider opencode |
kimi |
$flow-delegate with explicit provider kimi |
gemini |
$flow-delegate with explicit provider gemini |
kiro |
$flow-delegate with explicit provider kiro |
Procedure
- Parse only the legacy command name and user-supplied arguments. Use automatic provider selection only for
delegate; preserve the explicit provider for provider-named routes. - Report
ROUTE: <legacy> -> <canonical>. - Follow the canonical skill completely, including its inspection, safety, approval, artifact, and verification rules.
- Keep all new portable and operational state under
.planning/flow/; never translate Flow output back into.planning/fleet,.planning/delegation, or any other legacy layout. - When
initorsessionfinds.planning/config.jsonwithout.planning/flow/config.json, invoke the$flow-initmigration route and stop for approval after the read-only plan.
Constraints
- Compatibility never expands user authorization or bypasses canonical approval gates.
- Do not migrate files, enable audit, change Git, launch a fleet, install tools, or call external providers merely because a legacy command previously did so. Follow the routed skill's exact confirmation gates.
- Do not reuse legacy fleet bookkeeping, Docker projects, tmux sessions, branches, delegation output, or locks.
- Do not create one-off aliases or hidden compatibility 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 · 54 lines · 52 tokens per session scan A a9de21d31ccd
flow-compat 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 52 tokens to every session and 673 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.