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-productgit 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-product)<a href="https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/flow-product"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/flow-product/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-product"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/flow-product.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.00047 | $0.00417 |
| Opus 5 | $0.00023 | $0.00209 |
| Sonnet 5 | $0.00009 | $0.00083 |
| Haiku 4.5 | $0.00005 | $0.00042 |
Grade A, and why
flow-product 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 7d 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.
What it actually says
Plan product outcomes
Read product, artifacts, memory, and safety.
Route
- Use
prdwhen the problem, users, goals, scope, or requirements are not yet an approved product contract. - Use
roadmaponly when.planning/flow/product/prd.mdexists and its gate is approved.
PRD procedure
- Inspect existing product and repository context before interviewing.
- Ask one product decision at a time: problem, users, outcomes, non-goals, journeys, rules, requirements, risks, and release evidence.
- Label facts, user decisions, assumptions, dependencies, and open questions distinctly.
- Write the complete PRD using product.
- Trace each requirement with a stable ID.
- Present the PRD for explicit approval and stop. Do not generate a roadmap from an unapproved PRD.
Roadmap procedure
- Read the approved PRD and applicable project context.
- Build
Phase → Epic → Feature → Taskfrom outcomes rather than technical layers. - Give every node a parent, PRD requirement links, objective, acceptance outcome, dependencies, risks, estimate range, and status.
- Validate there are no orphan requirements or tasks and every phase delivers measurable value.
- Persist the hierarchy under
.planning/flow/product/roadmap/and present it for approval.
Work inline by default. A roadmap worker is allowed only when the user explicitly requests parallel agent work; the primary conversation owns approval.
Output
Return mode, artifact paths, traceability coverage, unresolved decisions, gate result, and next valid action.
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.
- 7d ago First seen · 37 lines · 47 tokens per session scan A b143f8286fef
flow-product is a skill published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (2 stars, last pushed today), licensed Apache-2.0. It adds 47 tokens to every session and 417 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.