brainstorming

brainstorming is a skill for Claude Code, Codex from 6BNBN/FlowPilot. It costs 37 tokens per session (1,035 once invoked), scanned A, a copy of brainstorming, MIT.

A guided process for turning an idea into an agreed software design before implementation. It explores the project, asks clarifying questions, compares possible approaches, and records the approved design.

In plain words
What is it for?
Use it before creating a feature, component, function, configuration change, or other behavior. It produces a design document in the project’s documentation area after the design is approved.
Why use it?
It exposes unclear requirements and design trade-offs before code changes make them expensive to correct. It creates a shared written reference for what will be built and why.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/6bnbn/flowpilot/brainstorming
Any agent
npx skills add 6BNBN/FlowPilot --skill brainstorming
Clone the repo
git clone --depth 1 https://github.com/6BNBN/FlowPilot

Made for: Claude Code, Codex.

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.

agentmods badge for brainstorming

README.md
[![agentmods](https://agentmods.dev/badge/skills/6bnbn/flowpilot/brainstorming.svg)](https://agentmods.dev/skills/6bnbn/flowpilot/brainstorming)
Your own site
<a href="https://agentmods.dev/skills/6bnbn/flowpilot/brainstorming"><img src="https://agentmods.dev/badge/skills/6bnbn/flowpilot/brainstorming.svg" alt="Measured on agentmods" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,035 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00037 $0.01035
Opus 5 $0.00018 $0.00517
Sonnet 5 $0.00007 $0.00207
Haiku 4.5 $0.00004 $0.00103

Measured 4d ago against content hash 795079a6c7b3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

brainstorming 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 4d 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.

Origin

This is a copy

100% identical to brainstorming — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

兼容codex@cursor一键安装技能/codex一键安装技能/.codex-home-claude-parity/skills/brainstorming/SKILL.md · 97 lines

How it starts

The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Brainstorming Ideas Into Designs

Overview

Help turn ideas into fully formed designs and specs through natural collaborative dialogue.

Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design and get user approval.

Anti-Pattern: "This Is Too Simple To Need A Design"

Every project goes through this process. A todo list, a single-function utility, a config change 閳?all of them. "Simple" projects are where unexamined assumptions cause the most wasted work. The design can be short (a few sentences for truly simple projects), but you MUST present it and get approval.

Checklist

You MUST create a task for each of these items and complete them in order:

  1. Explore project context 閳?check files, docs, recent commits
  2. Ask clarifying questions 閳?one at a time, understand purpose/constraints/success criteria
  3. Propose 2-3 approaches 閳?with trade-offs and your recommendation
  4. Present design 閳?in sections scaled to their complexity, get user approval after each section
  5. Write design doc 閳?save to docs/plans/YYYY-MM-DD-<topic>-design.md and commit
  6. Transition to implementation 閳?invoke writing-plans skill to create implementation plan

Process Flow

digraph brainstorming {
    "Explore project context" [shape=box];
    "Ask clarifying questions" [shape=box];
    "Propose 2-3 approaches" [shape=box];
    "Present design sections" [shape=box];
    "User approves design?" [shape=diamond];
    "Write design doc" [shape=box];
    "Invoke writing-plans skill" [shape=doublecircle];

    "Explore project context" -> "Ask clarifying questions";
    "Ask clarifying questions" -> "Propose 2-3 approaches";
    "Propose 2-3 approaches" -> "Present design sections";
    "Present design sections" -> "User approves design?";
    "User approves design?" -> "Present design sections" [label="no, revise"];
    "User approves design?" -> "Write design doc" [label="yes"];
    "Write design doc" -> "Invoke writing-plans skill";
}

Read the full file on GitHub · 97 lines

Changes

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.

  1. 4d ago First seen · 97 lines · 37 tokens per session scan A 795079a6c7b3

Subscribe to this mod's changes

brainstorming is a skill published in the GitHub repository 6BNBN/FlowPilot (133 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 1,035 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to brainstorming, differing in 14 lines, and is treated as a copy.

Related

Other skills, from other repositories

coding-agents-farm

To orchestrate parallel coding-agent farms (Claude, Codex, Copilot, Gemini, etc.) on isolated git worktrees.

griddynamics/rosetta · 32 tokens

nobrainer-ultra

Use when the owner says nb-ultra, nb-flow, nb-workflow, ultracode, or asks to set up, upgrade, or reconcile a project's agent workflow; or wants one non-trivial task taken from brief requirements through a complete skill-routed plan, guarded autonomous execution, useful multi-session work and final evidence audit.

nobrainer-tech/nobrainer-tech-skills · 73 tokens

nobrainer-autoimprove

Use when the owner says nb-autoimprove, deep-autoresearch, code-autoresearch, nobrainer-capture-lesson, or nobrainer-continuous-improvement; asks to improve a skill or prompt; or wants a measurable bounded baseline-variant-evaluation loop instead of one subjective rewrite.

nobrainer-tech/nobrainer-tech-skills · 70 tokens

nobrainer-dispatcher

Use when the owner says nb-dispatcher or nobrainer-dispatcher, or when an approved execution map has multiple queued work units that require ready-set selection, dependency-aware ordering, bounded parallel batches, retry scheduling, or routing audited results to the next queued unit; do not use for one coherent task…

nobrainer-tech/nobrainer-tech-skills · 89 tokens

nobrainer-writing

Use when the owner says nb-write, nobrainer-writing, nobrainer-style, or nobrainer-human-like, or asks to draft, rewrite, compress, humanize, edit, or review user-facing prose such as a message, comment, document, README, report, summary, email, post, or release note; maximize useful information per word without…

nobrainer-tech/nobrainer-tech-skills · 92 tokens

nobrainer-browser

Use when the owner says nb-browser or nobrainer-browser, asks to inspect or operate a rendered website, attach to an existing approved Chrome/Edge session, reproduce a browser flow, run Playwright tests, or record and analyze a Playwright trace. Prefer the latest Playwright CLI; do not set up MCP or extra browser…

nobrainer-tech/nobrainer-tech-skills · 75 tokens