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 Azzygoatcoder/agent-useful-skills --skill brainstorminggit clone --depth 1 https://github.com/Azzygoatcoder/agent-useful-skillsWrote 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/azzygoatcoder/agent-useful-skills/brainstorming)<a href="https://agentmods.dev/skills/azzygoatcoder/agent-useful-skills/brainstorming"><img src="https://agentmods.dev/badge/skills/azzygoatcoder/agent-useful-skills/brainstorming/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/azzygoatcoder/agent-useful-skills/brainstorming"><img src="https://agentmods.dev/badge/skills/azzygoatcoder/agent-useful-skills/brainstorming.svg" alt="Reviewed on agentmods" width="80" 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.00037 | $0.01936 |
| Opus 5 | $0.00018 | $0.00968 |
| Sonnet 5 | $0.00007 | $0.00387 |
| Haiku 4.5 | $0.00004 | $0.00194 |
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 9d 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 — 151 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.
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.
Fast Path: Small Changes
When the change is small and the intent is clear, keep the design discipline (the HARD-GATE still binds — no implementation before approval) but skip the documentation ceremony.
Take the fast path when ALL of these hold:
- Single component, config change, or a few files — not a new subsystem
- The user described the goal concretely ("add X to do Y"), not vaguely ("improve X")
- No architectural decisions or trade-offs that need comparison
- Roughly a day's work or less
Fast path flow:
- Brief context check — glance at the relevant files, not a full exploration
- Ask only what's genuinely ambiguous — at most 2-3 questions, batched into one message when they're simple
- Present a brief design — a few sentences: what you'll change, where, and any single real decision. Get explicit approval.
- Implement directly — skip the written spec doc, spec self-review, and user review gate. Track multi-step work with todos (or a short plan if it helps); for truly trivial single-step changes, just do it.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 151 lines · 37 tokens per session scan A 1a1d6e904210
brainstorming is a skill published in the GitHub repository Azzygoatcoder/agent-useful-skills (6 stars, last pushed 10d ago), licensed MIT. It adds 37 tokens to every session and 1,936 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
dsh-plugin-dev
An authoritative development guide for DeepSeek Harness plugins. DeepSeek Harness is a system where models, tools, services, events, and adapters are built as plugins.
dsh-plugin-client
A development guide for the browser interface of a DSH plugin, including its package structure, registered interface locations, and build setup.
dsh-plugin-dev
A guide for creating and debugging DeepSeek Harness plugins, which are add-ons packaged as npm modules with configuration files.
dsh-plugin-i18n
A pattern for giving a DSH plugin’s user interface English and Chinese text that changes immediately when the selected language changes.
dsh-git-commit
A Git commit guide for writing standardised commit messages and performing basic checks before committing code. Git commits are saved checkpoints in a project’s history.
dsh-dependency-audit
A guide for reviewing and upgrading project dependencies, which are third-party packages the project relies on. It covers security warnings, installation scripts, lock files, breaking changes, tests, rollback plans, and reducing unnecessary dependencies.