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 coctostan/pi-superpowers-plus --skill brainstorminggit clone --depth 1 https://github.com/coctostan/pi-superpowers-plusWrote 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/coctostan/pi-superpowers-plus/brainstorming)<a href="https://agentmods.dev/skills/coctostan/pi-superpowers-plus/brainstorming"><img src="https://agentmods.dev/badge/skills/coctostan/pi-superpowers-plus/brainstorming.svg" alt="Measured on agentmods" 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.00037 | $0.00752 |
| Opus 5 | $0.00018 | $0.00376 |
| Sonnet 5 | $0.00007 | $0.00150 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade A, and why
brainstorming 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 8d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Related skills: Consider
/skill:using-git-worktreesto set up an isolated workspace, then/skill:writing-plansfor implementation planning.
Brainstorming Ideas Into Designs
Overview
Help turn ideas into fully formed designs and specs through natural collaborative dialogue.
Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design in small sections (200-300 words), checking after each section whether it looks right so far.
Boundaries
- Read code and docs: yes
- Write to docs/plans/: yes
- Edit or create any other files: no
The Process
Before anything else — check git state:
- Run
git statusandgit log --oneline -5 - If on a feature branch with uncommitted or unmerged work, ask the user:
- "You're on
<branch>with uncommitted changes. Want to finish/merge that first, stash it, or continue here?"
- "You're on
- Require exactly one of: finish prior work, stash, or explicitly continue here
- If the topic is new, suggest creating a new branch before brainstorming
Understanding the idea:
- Check out the current project state first (files, docs, recent commits)
- Check if the codebase or ecosystem already solves this before designing from scratch
- Ask questions one at a time to refine the idea
- Prefer multiple choice questions when possible, but open-ended is fine too
- Only one question per message - if a topic needs more exploration, break it into multiple questions
- Focus on understanding: purpose, constraints, success criteria
Exploring approaches:
- Propose 2-3 different approaches with trade-offs
- Present options conversationally with your recommendation and reasoning
- Lead with your recommended option and explain why
Presenting the design:
- Once you believe you understand what you're building, present the design
- Break it into sections of 200-300 words
- Ask after each section whether it looks right so far
- Cover: architecture, components, data flow, error handling, testing
- Be ready to go back and clarify if something doesn't make sense
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.
- 8d ago First seen · 71 lines · 37 tokens per session scan A 444ff572d7a4
brainstorming is a skill published in the GitHub repository coctostan/pi-superpowers-plus (105 stars, last pushed 6mo ago), licensed MIT. It adds 37 tokens to every session and 752 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-08-30.
Other skills, from other repositories
omh-accessibility-audit
This is a Hermes-native accessibility-audit workflow skill.
omh-apple-design
This is a Hermes-native apple-design workflow skill.
conversational-ux
Design voice and conversational interfaces — dialog flows, error recovery, and persona. Use when the interface speaks and listens rather than being tapped. For graphical input collection, use form-design.
platform-conventions
Design to iOS and Android conventions — what each OS mandates, where they diverge, and when to unify. Use when shipping native apps. For breakpoint adaptation use responsive-design; for matching competitor patterns use jakobs-law (interaction-design).
design-negotiation
Advocate for design quality, scope, and timeline with partners and leadership using evidence and shared goals. Use in the conversation itself. For the commercial vocabulary behind it, use business-design (ux-strategy).
law-of-similarity
Apply the Law of Similarity — shared colour, shape, or size signals that elements belong to one category. Use when signalling relationships across distance. For grouping by position, use law-of-proximity.