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/ssbun/csl-agent-kit/brainstormingnpx skills add SSBun/csl-agent-kit --skill brainstorminggit clone --depth 1 https://github.com/SSBun/csl-agent-kitWrote 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/ssbun/csl-agent-kit/brainstorming)<a href="https://agentmods.dev/skills/ssbun/csl-agent-kit/brainstorming"><img src="https://agentmods.dev/badge/skills/ssbun/csl-agent-kit/brainstorming.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.00048 | $0.00581 |
| Opus 5 | $0.00024 | $0.00291 |
| Sonnet 5 | $0.00010 | $0.00116 |
| Haiku 4.5 | $0.00005 | $0.00058 |
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 today.
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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorming Ideas Into Designs
Turn ideas into validated designs through dialogue — before writing implementation code.
When to Use
- New feature or component with open design questions
- User asks to explore options, trade-offs, or requirements
- Scope or success criteria are not yet defined
Do not use for bug fixes, typo edits, or changes with an already-approved spec.
The Process
Understanding the idea:
- Check current project state (files, docs, recent commits)
- Ask questions one at a time to refine the idea
- Prefer multiple choice when possible; open-ended is fine
- Focus on purpose, constraints, and success criteria
Exploring approaches:
- Propose 2–3 approaches with trade-offs
- Lead with a recommendation and reasoning
Presenting the design:
- Break into sections of ~200–300 words
- Confirm after each section before continuing
- Cover architecture, components, data flow, error handling, testing
- Go back and clarify when something does not land
After the Design
Documentation:
- Do not create a standalone design file by default. Create one only when the user requests a document artifact or the validated design needs a durable handoff for later implementation.
- Before writing the artifact, require the owning canonical task ID. If it is missing, return to task activation instead of creating an unowned file.
- Ask for confirmation before persisting an inferred durable handoff; do not ask again when the user explicitly requested a design doc, plan file, RFC, or written spec.
- Write the validated design to
tasks/artifacts/<task-id>/specs/YYYY-MM-DD-<topic>-design.md. Keep that path when the design later becomes accepted, implemented, or superseded. - Add
../artifacts/<task-id>/specs/YYYY-MM-DD-<topic>-design.mdto the owning task record'sPlansection, then follow the task workflow's sync and check requirements. Do not copy the design body into the record. - Use clear, concise prose (no dependency on external writing skills)
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.
- today Changed · +1 lines b8c37ed53e4d
- 4d ago First seen · 57 lines · 48 tokens per session scan A af1d30a3e566
brainstorming is a skill published in the GitHub repository SSBun/csl-agent-kit (10 stars, last pushed 2d ago), licensed MIT. It adds 48 tokens to every session and 581 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…