Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/s977043/plangate/ai-dev-brainstorm)<a href="https://agentmods.dev/skills/s977043/plangate/ai-dev-brainstorm"><img src="https://agentmods.dev/badge/skills/s977043/plangate/ai-dev-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.1 | $0.00072 | $0.02965 |
| Opus 5 | $0.00036 | $0.01483 |
| Sonnet 5 | $0.00014 | $0.00593 |
| Haiku 4.5 | $0.00007 | $0.00297 |
Grade A, and why
ai-dev-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 7d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI-Driven Brainstorm (PlanGate / Codex 共用)
PlanGate ワークフローの brainstorm フェーズ を Codex / Claude Code 両方で実行する skill。
本スキルは bundled resources（
references/）で自己完結する。パス表記の規約（重要）: 本 SKILL.md 中の
references/…は、すべて 本スキル ディレクトリからの相対パス（=<skill_dir>/…）であって、導入先リポジトリのルートからの 相対パスではない。実行時はまず<skill_dir>（このファイルが置かれているディレクトリ）を 解決してから使う:
環境 <skill_dir>plugin 導入先（Claude marketplace） <plugin_root>/skills/ai-dev-brainstorm/install.sh --claude導入先.claude/skills/ai-dev-brainstorm/Codex 導入先 .codex/skills/ai-dev-brainstorm/上流リポジトリ（正本側） .agents/skills/ai-dev-brainstorm/導入先が独自の正本（上流リポジトリの
docs/配下に相当するもの）を別途保持している 場合は、そちらを優先すること。
Read First
参照解決順（導入先で必ずこの順に探す）
本 Skill は 上流リポジトリ基準の docs/** パスを直接参照しない（#1232）。docs/** は
install.sh --claude / plugin（Claude marketplace）/ Codex の 3 経路とも配布対象外であり、
書いた時点で導入先では必ず空振りするためである。参照の解決は次の順で行う:
<skill_dir>配下の同梱物（references/）を第一に読む — ワークフロー正本と実行契約は 本スキルに同梱されている（「同梱リファレンス」節の一覧）- 導入先リポジトリが独自の正本（上流の
docs/配下に相当するもの）を保持していれば、 そちらを優先する - rules（
rules/*.md）だけは配布経路によって着地が異なるため、次の順で探す:- 導入先リポジトリの相対パス（例:
.claude/rules/working-context.md）。 ただし 本 skill が参照する節（例:working-context.mdの「pbi-input.md」節）が実在することを確認する。同名でも別内容なら PlanGate の正本ではないため次へ進む - 無ければ plugin root 配下（例:
<plugin_root>/rules/working-context.md）。<plugin_root>は Bash でls "${CLAUDE_PLUGIN_ROOT}/rules/"を実行して展開・確認した 絶対パス（Read ツールは絶対パスを要求し環境変数を展開しないため、${CLAUDE_PLUGIN_ROOT}/...という文字列をそのまま Read しない）。変数が空・未設定ならキャッシュを glob で推測せず次へ進む
- 導入先リポジトリの相対パス（例:
- いずれでも解決できなければ 「正本
<path>を参照できなかった」と明示し、同梱references/と本 Skill の記述を代替正本として扱い、推測で内容を補わない
plugin root 直下に docs/ を探しに行かないこと: plugin が配布するのは
agents / commands / skills / rules 等の定義ディレクトリのみで docs/ を配布対象として
認識せず、plugin root 配下に相当する配布物が存在しないため必ず空振りする。
導入経路ごとに配置されるものが違う:
| 参照 | install.sh --claude 経由 |
plugin（Claude marketplace）経由 | Codex 経由 |
|---|---|---|---|
rules/*.md |
.claude/rules/ に着地（解決可） |
<plugin_root>/rules/ で解決 |
未配置（解決不可 → 手順 4 へ） |
| ワークフロー正本・実行契約 | <skill_dir>/references/ に同梱（解決可） |
<skill_dir>/references/ に同梱（解決可） |
<skill_dir>/references/ に同梱（解決可） |
scripts/** / bin/** |
コピー対象外（解決不可） | 目的の CLI は不在（解決不可） | 未配置（解決不可） |
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.
- 7d ago First seen · 142 lines · 72 tokens per session scan A 0312c4eff739
ai-dev-brainstorm is a skill published in the GitHub repository s977043/PlanGate (2 stars, last pushed yesterday), licensed MIT. It adds 72 tokens to every session and 2,965 once invoked, about $0.0004 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
merge-review
Reviews pending fleet worktree merges before they're accepted. Reads the merge-check queue, detects file-level conflicts between branches, proposes a safe merge order, and surfaces reconciliation plans for overlapping changes.
decision-map
Turn a loose idea into a git-tracked, session-resumable map of typed investigation tickets, then drive them to resolution one at a time. The planning-loop engine for work that is still being figured out — too fuzzy for a campaign, too big for a single intake item. Resolved tickets graduate into .planning/intake/ for…
01-sdlc
Autonomously orchestrates a request from framing to a draft pull request, isolating implementation, independent review, and final outcome challenge. Use when the user wants to deliver a change end to end. Not for running one development step.
02-backlog
Orchestrates a product backlog end to end. Use when the user wants to ask what it holds, or to run intake, triage, refinement, review, lifecycle events, ordering, health checks, or repair. Not for one known artifact step.
07-epic
Produces or refines an outcome-based Epic for a product backlog. Use when the user wants to frame, review, resume, or persist an Epic. Not for Product Briefs, User Stories, or implementation.
08-three-amigos
Assesses an Epic or Story through one product, delivery, or quality lens, then reconciles three caller-supplied reports. Use when the user wants to refine one before a backlog change. Not for spawning or writing.