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/hitmandark07/neatcodeai/brainstormingnpx skills add HITMANdark07/neatcodeai --skill brainstorminggit clone --depth 1 https://github.com/HITMANdark07/neatcodeaiWhat 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.00037 | $0.01828 |
| Opus 5 | $0.00018 | $0.00914 |
| Sonnet 5 | $0.00007 | $0.00366 |
| Haiku 4.5 | $0.00004 | $0.00183 |
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 2d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorming Ideas Into Designs
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.
Graph-aware preface
Before asking any clarifying question, route the idea through the graph.
This skill calls the query_graph MCP tool. The reason: design conversations should start from real precedent in the codebase, not abstract intuition. If the user says "let me add a thing that does X," the codebase very likely already does something close to X — and the design should either follow that pattern or explicitly diverge from it with a stated reason.
Procedure:
-
Pull the noun phrases out of the user's request (subject, verb, target).
-
Call
query_graphfor each phrase. Capture the top hits withfile:linecitations. -
If hits exist, surface them in a short "existing patterns" block before the first clarifying question:
Found 3 existing patterns that look related:
services/billing/InvoiceProcessor(src/services/billing/invoice-processor.ext:42)services/billing/PaymentReconciler(src/services/billing/payment-reconciler.ext:18)lib/queue/JobRunner(src/lib/queue/job-runner.ext:9)
Should the new component follow the same shape, or are we deliberately doing something different?
-
If no hits, say so: "No close patterns in the graph — this is greenfield in this repo." Then proceed to clarifying questions.
The first clarifying question becomes much sharper when grounded in what already exists. Skip this step only if the request is purely a configuration tweak with no code surface.
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.
- 2d ago First seen · 140 lines · 37 tokens per session scan A ee8e0a492be6
brainstorming is a skill published in the GitHub repository HITMANdark07/neatcodeai (0 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 1,828 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…