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-brainstormgit 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-brainstorm)<a href="https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/power-brainstorm"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/power-brainstorm/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-brainstorm"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/power-brainstorm.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.00033 | $0.00919 |
| Opus 5 | $0.00016 | $0.00460 |
| Sonnet 5 | $0.00007 | $0.00184 |
| Haiku 4.5 | $0.00003 | $0.00092 |
Grade A, and why
power-brainstorm 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorm Before Building
Read collaboration, artifacts, and context before acting.
If the codebase map exists, read .planning/power/context/project.md and
.planning/power/context/domain.md first. They tell you the
architecture you are extending and the words this code already uses — proposing Patient where
the code says Beneficiary produces a design nobody can map onto the repository. The map informs;
it never decides. Where it disagrees with the code, the code is right and the map is stale.
Step 1 — Classify, out loud, before the first question
Say which path this is and why, in one sentence, before you ask anything. The classification determines how much process follows, so hiding it hides the decision.
| Path | What it is | Where it ends |
|---|---|---|
| Spike | A feasibility question. You do not know if something is possible. | A recommendation. Any code is labelled throwaway. |
| Bounded | A well-scoped change to a flow that already exists in this repository. | Agreement in chat. No spec file, no plan. |
| Architectural | New systems, new subsystems, interface changes, anything you cannot fully picture yet. | An approved spec.md, then power-plan. |
Bounded means you can read the flow you are about to change. Understanding what kind of application it is does not make a change bounded.
The ratchet. When torn between two paths, take the heavier one. Hidden complexity found mid-task moves you up a path; nothing ever moves you down. A bounded change that turns out to need a new interface becomes architectural at that moment, and you say so.
Spike
State the question and a two-or-three-sentence probe plan. Get a nod. Investigate the cheapest way that actually answers it. Report what you found and what you recommend. Say explicitly that any code written is throwaway.
Bounded
Ask what you need, one question at a time. Read the existing flow. Present a short design in the conversation — no file. Then stop. Implement only after an explicit yes.
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 · 89 lines · 33 tokens per session scan A 2595ad305398
power-brainstorm is a skill published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (2 stars, last pushed today), licensed Apache-2.0. It adds 33 tokens to every session and 919 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.