Borrowing it
Nothing to install: this file belongs to akaghef/M3E. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/akaghef/M3E/main/.claude/skills/brainstorm/SKILL.mdgit clone --depth 1 https://github.com/akaghef/M3EWrote 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/akaghef/m3e/brainstorm)<a href="https://agentmods.dev/skills/akaghef/m3e/brainstorm"><img src="https://agentmods.dev/badge/skills/akaghef/m3e/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/akaghef/m3e/brainstorm"><img src="https://agentmods.dev/badge/skills/akaghef/m3e/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.00256 | $0.04152 |
| Opus 5.5 | $0.00102 | $0.01661 |
| Sonnet 5.5 | $0.00051 | $0.00830 |
| Haiku 4.5 | $0.00026 | $0.00415 |
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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
brainstorm — docs/ideas/ ブレスト展開スキル
ユーザーの思いつきを docs/ideas/<group>/<topic>/ フォルダに展開する。
採否は決めない・実装詳細は決めない・複数案を並べる が大原則。
レビュー前のアイデアプール段階。後でユーザーが選択肢から選んで実装方針を確定する。
いつ使うか
- 新しい機能アイデアや概念を整理したい
- 「決めずに広く考えたい」段階
- 後でレビューする前提で網羅性を優先したい
- 複数のテーマを横断的に並べたい
逆に 使わない 場面:
- 既に方針が決まっている実装タスク（普通にコードを書く）
- 短い思いつきメモ（
tomdskill を使う、またはm3e-scratchskill） - 即座にマップに残したいだけのアイデア（
m3e-scratchskill）
出力構造
docs/ideas/<group>/<topic>/
├── README.md # 索引 + 全体俯瞰 + 論点一覧
├── 01_<theme>.md # 第一の切り口（コンセプト/ユースケース等）
├── 02_<theme>.md # 第二の切り口（実装方式の選択肢）
├── 03_<theme>.md # 第三の切り口（UI/体験のバリエーション）
├── 04_<theme>.md # 第四の切り口（データ/永続化）
└── 05_<theme>.md # 最終ファイル（MVP/未決質問/戦略）
<group> は 必ず以下のメタフォルダのいずれか を選ぶ:
| メタフォルダ | 守備範囲 | 既存トピック例 |
|---|---|---|
00_meta/ |
M3E 自身に関するメタ機能・自己改善・自動化障害 | meta_m3e, automation_obstacles |
10_io/ |
入出力・取り込み・公開・外部ツール統合 | capture_ingest, export_publish, tool_integration |
20_ai/ |
AI エージェント・LLM 連携・思考パートナー | ai_agent_deep |
30_ux/ |
UI・操作・可視化・体験・ゲーム化 | slideshow, keyboard_modes, map_views, gamification |
40_data/ |
データ・履歴・性能・整理・スケール | maintenance_hygiene, time_history, performance_scale |
50_collab/ |
協調・デバイス連携・セキュリティ・プライバシー | collaboration, cross_device, privacy_security |
60_workflow/ |
研究・学習・生産性・教育プロセス | personal_productivity, cognitive_science, education |
70_concept/ |
思想・哲学・隠喩・実験的コンセプト | thought_physics, philosophical |
新ブレスト開始時に必ずメタフォルダを判定する（鉄則 0）。 複数候補がある場合は最も中心的なものを選び、その判断理由を README に 1 行残す。 どこにも収まらない新領域なら、新メタフォルダ追加をユーザーに提案する（自動で増やさない）。
ファイル数の目安: 5〜8ファイル（README含む）。 1ファイル500〜2000行程度。短すぎず長すぎず。
標準テンプレート
過去事例で実証済みの構成パターン:
Pattern A: 機能アイデア展開（slideshow 型）
01_concept.md — 何か、なぜ、ユースケース、既存ツール差分
02_options.md — 実装方式の選択肢（決めない）
03_runtime_ui.md — UI / 体験のバリエーション
04_data_model.md — データモデル / 永続化 / 互換性
05_mvp_path.md — 最小実装案 + 未決質問 + 段階導入ロードマップ
Pattern B: 候補列挙型（keyboard_modes / map_views 型）
01_global_design.md — 共通論点（命名規約・分類軸）
02_<group1>.md — グループ1 の候補列挙
03_<group2>.md — グループ2 の候補列挙
...
N_implementation.md — 横断: 共通基盤・優先順・実装方針
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 · 277 lines · 256 tokens per session scan A 8961a88b2c5b
brainstorm is a skill published in the GitHub repository akaghef/M3E (11 stars, last pushed 5d ago), licensed MIT. It adds 256 tokens to every session and 4,152 once invoked, about $0.0010 per session on Opus 5.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-10-02.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…