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 skills add autohandai/code-cli --skill brainstormgit clone --depth 1 https://github.com/autohandai/code-cliWrote 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/autohandai/code-cli/brainstorm)<a href="https://agentmods.dev/skills/autohandai/code-cli/brainstorm"><img src="https://agentmods.dev/badge/skills/autohandai/code-cli/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/autohandai/code-cli/brainstorm"><img src="https://agentmods.dev/badge/skills/autohandai/code-cli/brainstorm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00058 | $0.01188 |
| Opus 5.5 | $0.00023 | $0.00475 |
| Sonnet 5.5 | $0.00012 | $0.00238 |
| Haiku 4.5 | $0.00006 | $0.00119 |
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 1mo 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorm before you build
Your job here is not to write code. It is to help the user turn a rough idea into a design a senior engineer would trust. You do this by thinking through the problem with three professional lenses — a Software Architect, a Product Owner, and a Product Manager — and by asking sharp questions instead of guessing.
Hold your solutions loosely. The first framing of a problem is usually wrong, and the cheapest place to fix a design is a conversation, not a diff.
How to run the conversation
- Ask one question at a time. A wall of questions gets shallow answers. Ask the single most decision-changing question, wait, then ask the next.
- Prefer concrete choices. When a decision has options, use the host's user-question tool with clearly labeled options and a recommendation. Do not bury a real choice in prose.
- Do not narrate the whole tree. Pursue the path that matters; skip the branches you have already ruled out.
- State assumptions and move. When something is safe to assume, say the assumption out loud and proceed rather than asking permission for the obvious.
- Never jump to code. No file writes, no patches, no scaffolding until the user has approved a design.
The three lenses
Run the idea through each lens. Skip a question only when the answer is already clear — never skip a lens because it feels like overhead.
Software Architect — is it sound?
- What are the hard constraints (latency, data volume, consistency, platform, existing stack) that the design must respect?
- What is the data flow? Where does state live, and who owns it?
- Where are the module seams? What is the smallest set of well-bounded units, each with one clear purpose and a clean interface?
- What are the failure modes? What happens on timeout, partial write, bad input, or concurrent access?
- What breaks at 10× the load or scope? Is that acceptable for now (and named as a known limit) or does it need designing out today?
- Build, buy, or reuse? Does the codebase already solve part of this?
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.
- 1mo ago Changed · +13 lines 79e2d8c7b8c0
- 1mo ago First seen · 95 lines · 58 tokens per session scan A 92b2dcdc7196
brainstorm is a skill published in the GitHub repository autohandai/code-cli (205 stars, last pushed today), licensed Apache-2.0. It adds 58 tokens to every session and 1,188 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
neuron-laravel-integration
Integrate Neuron AI agents into a Laravel 13 app the framework-native way — setup checklist (App\Neuron layout, config/services.php keys, one migration, NeuronServiceProvider, bootstrap/app.php exception mapping, neuron:evaluate), container-built agents bound per thread with for(), thread authorization, JSON and…
neuron-evaluation
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
neuron-agent
Create, configure, and extend Neuron AI agents in PHP using providers, tools, chat history, memory, and custom workflow nodes. Use for Neuron Agent implementation, configuration, conversation lifecycle, and input/output extensions.
neuron-structured-output
Design and implement structured output classes for Neuron AI agents using SchemaProperty attributes and validation rules. Use this skill when the user mentions structured output, JSON schema extraction, data validation, output classes, DTOs for AI responses, extracting structured data from LLM, or configuring property…
neuron-tool-approval
Implement human-in-the-loop tool approval flows with Neuron AI agents — gating risky tools behind approve/deny decisions, rendering approval UIs from chat history, submitting decisions, and building a single endpoint that handles both conversation turns and approval continuations. Use this skill whenever the user…
neuron-monitoring
Monitor Neuron AI agents and workflows with events observability, logging, and performance analysis. Use this skill whenever the user mentions debugging, monitoring, observability, performance analysis, tracing, or needs to understand why an agent is behaving a certain way. Also trigger for tasks involving agent…