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 a-ariff/ariff-claude-plugins --skill brainstorminggit clone --depth 1 https://github.com/a-ariff/ariff-claude-pluginsWrote 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/a-ariff/ariff-claude-plugins/brainstorming)<a href="https://agentmods.dev/skills/a-ariff/ariff-claude-plugins/brainstorming"><img src="https://agentmods.dev/badge/skills/a-ariff/ariff-claude-plugins/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.00013 | $0.00475 |
| Opus 5 | $0.00006 | $0.00237 |
| Sonnet 5 | $0.00003 | $0.00095 |
| Haiku 4.5 | $0.00001 | $0.00047 |
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 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
Brainstorming → Design
Purpose
Turn vague ideas into actionable designs through Socratic questioning.
"I'm using the Brainstorming skill to refine your idea into a design."
The Flow
[Idea] → Phase 1: Understand → Phase 2: Explore → Phase 3: Design → [Plan]
Phase 1: Understanding (Ask Questions)
One question at a time. Prefer multiple choice.
Questions to ask:
- What problem does this solve?
- Who's the user?
- What's success look like?
- Any constraints (time, tech, integrations)?
- What's already built that this touches?
Before asking: Check working directory for existing context.
Phase 2: Exploration (Present Options)
Present 2-3 approaches:
### Approach A: [Name]
- Architecture: [how it works]
- Pros: [benefits]
- Cons: [tradeoffs]
- Complexity: [low/medium/high]
### Approach B: [Name]
...
Ask: "Which approach resonates? Or should we explore others?"
Phase 3: Design (Incremental)
Present design in 200-300 word chunks:
- Architecture overview
- Key components
- Data flow
- Error handling
- Testing strategy
After each chunk: "Does this look right?"
Phase 4: Handoff
When design approved:
"Ready to create the implementation plan?"
If yes → Use writing-plans skill
Going Backwards
It's okay to revisit earlier phases:
- New constraint discovered → Back to Phase 1
- Design doesn't feel right → Back to Phase 2
- Missing requirements → Back to Phase 1
Don't force linear progress.
Principles
- YAGNI - Don't design what's not needed
- Explore alternatives - Never settle on first idea
- Validate incrementally - Small chunks, frequent feedback
- Document decisions - Why, not just what
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 · 86 lines · 13 tokens per session scan A 84b67f71b972
brainstorming is a skill published in the GitHub repository a-ariff/ariff-claude-plugins (14 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 475 once invoked, about $0.0001 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
web-artifacts-builder
Modern web development patterns using React + Tailwind CSS + shadcn/ui for building production-quality, accessible, and performant web applications.
frontend-aesthetics
Distinctive frontend design principles for avoiding generic AI defaults, implementing thoughtful typography/color/animations, and creating polished user experiences based on Claude Code design research.
gui-design-principles
Comprehensive design principles and best practices for creating beautiful, functional GUI applications including dashboards, web apps, and mobile apps.
skin-creator
Create and apply a two-asset LobsterAI visual skin from the user's style description. Use only when the AI Skin Designer kit supplies the structured skinpack workflow marker; do not use for ordinary theme or image requests.
data-viz-renderer
Generate self-contained HTML/SVG infographics from JSON data, including stat cards, bar charts, flow diagrams, and mixed dashboards. Offers 8 color palettes and built-in icons with no external dependencies. Triggered when users request data visualization, infographics, charts, or dashboards.
canvas-design
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.