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 majiayu000/spellbook --skill brainstorminggit clone --depth 1 https://github.com/majiayu000/spellbookWrote 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/majiayu000/spellbook/brainstorming)<a href="https://agentmods.dev/skills/majiayu000/spellbook/brainstorming"><img src="https://agentmods.dev/badge/skills/majiayu000/spellbook/brainstorming/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/majiayu000/spellbook/brainstorming"><img src="https://agentmods.dev/badge/skills/majiayu000/spellbook/brainstorming.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.00032 | $0.00800 |
| Opus 5 | $0.00016 | $0.00400 |
| Sonnet 5 | $0.00006 | $0.00160 |
| Haiku 4.5 | $0.00003 | $0.00080 |
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 5d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorming
From obra/superpowers
Purpose
Turn rough ideas into fully-formed designs through collaborative dialogue, NOT immediate implementation.
Use for: Exploring ideas, designing features, architecture decisions NOT for: Clear mechanical processes with obvious implementation
The Three Phases
Phase 1: Understanding the Idea
-
Review existing context
- Read relevant project files
- Understand current architecture
- Note constraints and requirements
-
Ask clarifying questions
- ONE question at a time
- Prefer multiple choice when possible
- Open-ended questions are fine too
- Wait for answer before next question
Good: "Should this feature support offline mode?
A) Yes, full offline support
B) Yes, limited offline (read-only)
C) No, online only"
Bad: "What about offline support? And caching?
Also, how should errors be handled?"
Phase 2: Exploring Approaches
- Present 2-3 different solutions
- Each with clear trade-offs
- Lead with recommended option
- Explain reasoning
## Approach A: Event-Driven (Recommended)
- Pros: Decoupled, scalable, easy to extend
- Cons: More complex debugging, eventual consistency
- Best for: Systems needing flexibility
## Approach B: Direct Integration
- Pros: Simple, immediate consistency
- Cons: Tight coupling, harder to scale
- Best for: Small, stable systems
## Approach C: Hybrid
- Pros: Balance of both
- Cons: Complexity of managing two patterns
- Best for: Gradual migration scenarios
- Discuss trade-offs
- Performance vs simplicity
- Flexibility vs maintainability
- Short-term vs long-term
Phase 3: Presenting the Design
-
Present in sections (200-300 words each)
- Architecture overview
- Key components
- Data flow
- Error handling
- Testing strategy
-
Validate incrementally
- Get confirmation after each section
- Adjust based on feedback
- Don't dump everything at once
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.
- 5d ago First seen · 144 lines · 32 tokens per session scan A f3a8625ef55d
brainstorming is a skill published in the GitHub repository majiayu000/spellbook (277 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 800 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
pneuma-session
Instructions for renaming an active Pneuma session and replacing its default preview with a useful title and summary. A Pneuma session is one work area inside a larger project.
pneuma-preferences
Persistent user preference memory across sessions. Consult this skill BEFORE making any design, style, or aesthetic decisions — choosing colors, themes, layouts, fonts, tone of voice, content density, or visual direction. Also consult when starting a new creative task in any mode, when the user corrects your style…
session-handoff
Use when the user wants to hand off, transfer, pause, or continue the current session in a new session or with another agent — asks for a "session handoff", a "prompt para a próxima sessão", to "continuar de onde paramos", or invokes /session-handoff; also when context is running low and in-flight work must survive a…
Cursor rules for avoiding placeholder or broken image URLs, using stable visual
Cursor rules for avoiding placeholder or broken image URLs, using stable visual assets, and checking alt text, dimensions, licensing, and responsive behavior.
Tailwind CSS Patterns
Use this skill when styling UI with Tailwind and you want consistent design tokens, maintainable class composition, and good accessibility defaults.
Cursor rules for embedding Beefree SDK's no-code content editors (for emails, pa
Cursor rules for embedding Beefree SDK's no-code content editors (for emails, pages, and popups) into a web application.