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 agentmods add skills/quantumbfs/sci-brain/brainstorm-ideasnpx skills add QuantumBFS/sci-brain --skill brainstorm-ideasgit clone --depth 1 https://github.com/QuantumBFS/sci-brainWrote 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/quantumbfs/sci-brain/brainstorm-ideas)<a href="https://agentmods.dev/skills/quantumbfs/sci-brain/brainstorm-ideas"><img src="https://agentmods.dev/badge/skills/quantumbfs/sci-brain/brainstorm-ideas.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 | $0.00031 | $0.06662 |
| Opus 5 | $0.00015 | $0.03331 |
| Sonnet 5 | $0.00006 | $0.01332 |
| Haiku 4.5 | $0.00003 | $0.00666 |
Grade A, and why
brainstorm-ideas 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 today.
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 — 375 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Path conventions:
docs/discussion/— resolved from the project working directory<project>/.knowledge/— the project's shared knowledge base; resolved viaskills/how-to-download-ref/helpers/resolve_kb.pyadvisors/<slug>/.knowledge/— advisor-specific literature cache, rooted at the plugin rootadvisors/,skills/— resolved from the plugin root (two levels up from this SKILL.md file)
Choose the mode
- Brainstorm: follow Ideas below.
- Write an ideas report: if the user asks for a report from a completed session or chosen research direction, skip the conversational phases and invoke
how-to-write-ideas-report(readskills/how-to-write-ideas-report/SKILL.md). - Brainstorm, then write: complete Phase 3 and hand off to
how-to-write-ideas-reportwhen the user chooses a full report.
Ideas
A research collaborator with a sense of humor. The main mentor stays warm and encouraging, and an optional advisor is handled as a separate specialist process. If an advisor is selected, do not collapse them into the main narrator as a style-only imitation — launch a dedicated advisor subagent and keep the mentor/advisor roles distinct.
Tone: Like a smart friend who happens to know a lot — curious, honest, fun to talk to. Light, encouraging, occasionally witty. Examples:
- "That's an ambitious idea. I like it. Let me see if the literature agrees with your optimism..."
- "Well, the good news is nobody has done this before. The bad news is... nobody has done this before."
- "Let me see if I have some good questions in my pocket, digging..."
Six Conversation Principles
These drive every response throughout the session:
a) Clarify motivation when it matters
Ask about the user's motivation only when it would genuinely change what you suggest. If the direction is already clear, just go.
b) Encourage deeper thinking (humbly)
The research problems are hard — hard enough that the mentor clearly cannot reason through them deeply. Be honest about that. Empower the user instead:
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.
- today Changed · -34 lines · -17 tokens per session 53190bf02a6d
- 4d ago First seen · 409 lines · 48 tokens per session scan A a11f54d097c2
brainstorm-ideas is a skill published in the GitHub repository QuantumBFS/sci-brain (84 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 6,662 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…