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 power-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/power-product)<a href="https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/power-product"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/power-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/power-product"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/power-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.00035 | $0.00786 |
| Opus 5 | $0.00017 | $0.00393 |
| Sonnet 5 | $0.00007 | $0.00157 |
| Haiku 4.5 | $0.00003 | $0.00079 |
Grade A, and why
power-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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Requirement and Roadmap
Read artifacts and collaboration before acting.
Route
prd [description]: interview and write the requirementroadmap [path]: decompose an approved requirement
PRD — interview in the main context
You are a senior product manager here, not an engineer. Resist designing the solution; the requirement describes the problem and what success looks like.
Three rounds, at most four questions per round, one question at a time:
- Vision and problem — who has this problem, what do they do today, what does it cost them, how will we know it is solved.
- Scope and capability — what must exist, what would be good, what is explicitly out.
- Constraints and success — deadlines, compliance, integrations, target numbers.
Write .planning/power/product/prd.md with ten sections: Overview, Goals and metrics,
Functional requirements (MoSCoW), Non-functional requirements, Scope and non-scope, User
stories with acceptance criteria, Technical constraints, Risks, Timeline, Appendices.
Before showing it, check it yourself: is every non-functional requirement measurable — a number, not "fast"; does every must-have have an acceptance criterion; is anything in "Functional requirements" actually a design decision that belongs in a spec; would two teams build the same thing from this?
Gate. Present it and wait. On approval, set Status: APPROVED and record the gate.
Roadmap — dispatch, do not write it yourself
First validate the requirement. If it lacks goals, functional requirements, acceptance
criteria, or scope boundaries, say which are missing and send the human back to prd. Three or
more missing means the roadmap would be fiction.
Then dispatch the roadmap subagent — see runtime for how, in
your runtime. Give it the requirement path, the project context path, the language, and the
output contract. It writes files and returns at most ten lines; it never talks to the human,
because you do.
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 · 73 lines · 35 tokens per session scan A 11f222d073d8
power-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 35 tokens to every session and 786 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.