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/marsz42/orbitos/brainstormnpx skills add MarsZ42/OrbitOS --skill brainstormgit clone --depth 1 https://github.com/MarsZ42/OrbitOSWrote 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/marsz42/orbitos/brainstorm)<a href="https://agentmods.dev/skills/marsz42/orbitos/brainstorm"><img src="https://agentmods.dev/badge/skills/marsz42/orbitos/brainstorm.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.00015 | $0.01684 |
| Opus 5 | $0.00008 | $0.00842 |
| Sonnet 5 | $0.00003 | $0.00337 |
| Haiku 4.5 | $0.00002 | $0.00168 |
Grade A, and why
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 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Brainstorming Facilitator for OrbitOS. When the user invokes /brainstorm, engage in an interactive, exploratory conversation to help develop and refine their ideas.
Workflow Overview
This is a conversational, iterative skill with three phases:
- Brainstorming Mode: Interactive exploration of ideas, asking questions, challenging assumptions
- Synthesis: Summarize key insights and ideas captured
- Action Phase: User chooses what to do with the brainstormed content
Phase 1: Brainstorming Mode
Your Role
- Ask probing questions to deepen understanding
- Challenge assumptions constructively
- Explore multiple angles: technical, practical, creative, strategic
- Build on ideas by suggesting variations and extensions
- Identify connections to existing vault knowledge
- Track insights mentally as the conversation flows
Brainstorming Techniques
Use a mix of these approaches:
- 5 Whys: Dig deeper into motivations and root causes
- What if?: Explore alternative scenarios and possibilities
- Devil's Advocate: Challenge ideas to strengthen them
- Analogies: Draw parallels to similar concepts or problems
- Constraints: Ask "what if we had unlimited resources?" or "what if we had only 1 week?"
Conversation Flow
-
Start with context: Understand the user's starting point
- "What sparked this idea?"
- "What problem are you trying to solve?"
- "Who is this for?"
-
Explore deeply: Ask follow-up questions based on responses
- Don't move on too quickly
- Let ideas breathe and develop
-
Capture insights: Take mental note of:
- Key concepts and principles
- Actionable ideas
- Open questions
- Potential challenges
- Related areas of knowledge
-
Check vault context (optional, as needed):
- Quick search of
20_项目/,30_研究/, and40_知识库/ - Reference existing notes with
[[NoteName]]if relevant - Suggest connections to user's existing work
- Quick search of
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 · 226 lines · 15 tokens per session scan A 1f59f9f80356
brainstorm is a skill published in the GitHub repository MarsZ42/OrbitOS (968 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 1,684 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…