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 justnau1020/claude-os --skill brainstormgit clone --depth 1 https://github.com/justnau1020/claude-osWrote 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/justnau1020/claude-os/brainstorm)<a href="https://agentmods.dev/skills/justnau1020/claude-os/brainstorm"><img src="https://agentmods.dev/badge/skills/justnau1020/claude-os/brainstorm/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/justnau1020/claude-os/brainstorm"><img src="https://agentmods.dev/badge/skills/justnau1020/claude-os/brainstorm.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.00038 | $0.01423 |
| Opus 5 | $0.00019 | $0.00711 |
| Sonnet 5 | $0.00008 | $0.00285 |
| Haiku 4.5 | $0.00004 | $0.00142 |
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 10d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorm
Guided ideation pipeline that turns rough ideas into a validated requirements document. Alternates between conversation with the user and delegated research to keep main context lean.
Invocation
/brainstorm [topic or idea]
Examples:
/brainstorm "real-time notifications system"/brainstorm "mobile-responsive dashboard"/brainstorm "plugin marketplace monetization"
Pipeline
Phase 1: Idea Exchange (Main + User)
NO agents. NO file reads. Just conversation.
Main's job:
- Listen to the user's idea
- Ask clarifying questions to understand intent (not implementation):
- What problem does this solve?
- Who benefits?
- What does success look like from the user's perspective?
- Rephrase the idea back to confirm understanding
- If the user has multiple ideas, list them all before researching any
Output: A numbered list of candidate ideas, each 1-2 sentences.
Context budget: This phase should use <500 tokens of main's context.
Phase 2: Research Gates (Parallel Agents)
For EACH candidate idea from Phase 1, spawn research agents in parallel. Main does NOT read their raw output -- agents return a structured verdict.
Agents per idea (launch all in parallel):
| Agent | Question | Method | Verdict format |
|---|---|---|---|
feasibility |
"Can our stack do this?" | Read architecture docs, relevant source files | FEASIBLE / RISKY / INFEASIBLE + 2-line reason |
prior-art |
"How do serious players solve this?" | Web search for established approaches | 3 bullet points: who does it, how, what we can learn |
conflict-check |
"Does this break or duplicate anything we have?" | Read architecture docs, grep for overlapping features | CLEAR / CONFLICT + what it conflicts with |
Agent prompt template:
You are a research agent. Answer ONE question and return a structured verdict.
QUESTION: [question]
IDEA: [idea description]
PROJECT: [brief context from Phase 1]
Research approach:
- [specific files to read or searches to run]
Return your verdict in EXACTLY this format:
VERDICT: [FEASIBLE|RISKY|INFEASIBLE] or [CLEAR|CONFLICT] or [bullet points]
REASON: [2-3 lines max, be specific, cite what you found]
Do NOT return raw file contents or search results. Only the verdict.
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.
- 10d ago First seen · 163 lines · 38 tokens per session scan A 1b6246d98525
brainstorm is a skill published in the GitHub repository justnau1020/claude-os (3 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 38 tokens to every session and 1,423 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-31.
Other skills, from other repositories
skill-curator
A Chinese-language evaluator for deciding whether developer tools and agent resources are suitable for a curated collection. It checks real repositories, installation paths, activity, duplicates, and security boundaries using evidence.
env-manager
An environment-variable manager for project settings stored outside the code, often in .env files. It checks variable definitions and usage while keeping secret values out of reports and terminal output.
git-workflow
A guide for handling Git repository work safely, including status checks, branches, commits, pushes, pull requests, and rebasing. Git is a version-control system that records code changes and coordinates work between developers.
perf-profiler
A performance investigation guide that uses repeatable measurements and profiling evidence to find where software spends time or resources. Profiling records runtime activity such as CPU use, memory use, database work, or network delays.
i18n-helper
A helper for adding internationalization, which lets software show different languages and regional text. It finds user-visible text written directly in code and moves it into language files.
log-analyzer
A log-analysis helper that reads application and system logs to find unusual patterns and likely causes. Logs are records of events such as errors, requests, warnings, and service activity.