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 ayberkcansever/ai-skills --skill brainstormgit clone --depth 1 https://github.com/ayberkcansever/ai-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/ayberkcansever/ai-skills/brainstorm)<a href="https://agentmods.dev/skills/ayberkcansever/ai-skills/brainstorm"><img src="https://agentmods.dev/badge/skills/ayberkcansever/ai-skills/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/ayberkcansever/ai-skills/brainstorm"><img src="https://agentmods.dev/badge/skills/ayberkcansever/ai-skills/brainstorm.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.00036 | $0.02531 |
| Opus 5.5 | $0.00014 | $0.01012 |
| Sonnet 5.5 | $0.00007 | $0.00506 |
| Haiku 4.5 | $0.00004 | $0.00253 |
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 — 149 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.
Short Lane — when the full chain is disproportionate
The design gate above never lifts. What can be skipped is the planning chain after it (interview-plan → write-plan). A change takes the short lane only when ALL hold:
- Touches at most 2 files and roughly 50 lines; no new module, table, endpoint, or job.
- No behaviour change observable by users, operators, or downstream systems — no alert text, API shape, schedule, threshold, or default that gates an action.
- No new decision — the existing spec/design already covers it, or the change is mechanical (typo, rename, dependency bump, a constant whose value was already decided).
- Not on a production-critical path: money, auth, deploy, data migration, production alerting.
Short lane = design in 2–3 sentences + how it will be verified → user approval → write docs/specs/<TICKET-ID>/spec.md holding only a ## Decisions section with the 1–3 decisions as D<n>. <one line> + Check: <gate command> (the Spec File Template layout from interview-plan's references/interview-reference.md; cite an existing D<n> when a spec for this ticket already has it) → implement → commit with Lane: short — <reason> in the body so the lane choice is auditable from git log → run thermo-nuclear-code-quality-review on the committed diff → fix commits until Verdict: ship. Commit before review: the review refuses a dirty tree. The review sweeps spec.md for D<n> lines — a prose design.md alone leaves it nothing to check and caps the verdict at fix-first. Any doubt on any bullet → full chain. Choosing the lane is a decision: say it out loud with the reason, never assume it.
What ships with it
6 files 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.
- 1mo ago Changed · +12 lines 0cf911975b5c
- 1mo ago Changed · -30 lines 0eca3185c837
- 1mo ago First seen · 167 lines · 36 tokens per session scan A c4ab51840104
brainstorm is a skill published in the GitHub repository ayberkcansever/ai-skills (2 stars, last pushed 25d ago), licensed MIT. It adds 36 tokens to every session and 2,531 once invoked, about $0.0001 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-31.
Other skills, from other repositories
fetch-url
Fetch a single URL and print its content as Markdown. Use when you need to read a web page, documentation page, or API reference without indexing it. Accepts http(s):// and file:// URLs and writes the result to stdout.
firebase-messaging
Use when setting up Firebase Cloud Messaging, managing permissions and tokens, handling background/foreground notification taps, or dispatching messages server-side (HTTP v1).
firebase-cloud-functions
Use when calling callable functions (httpsCallable), passing data to server-side logic, handling function errors/timeouts, configuring regions, or testing with the Emulator Suite.
accessibility
Use when working on accessibility, a11y, WCAG, ARIA, screen readers, keyboard nav, focus order, contrast, alt text, captions, reduced motion, or target sizes; not language/culture/device (see inclusive-design).
karpathy-llm-wiki
Use when building or maintaining a personal LLM-powered knowledge base. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki quality, 'add to wiki', 'what do I know about', or any mention of 'LLM wiki' or 'Karpathy wiki'.
excalidraw-architect
Choose and compose the right Excalidraw diagram - architecture, flowchart, sequence, state, ER, swimlane, process, timeline, quadrant, pyramid, venn, loop, gantt, bar, line, scatter, and more - using the excalidraw-architect-mcp server. Use whenever a reader would learn more from a picture than from prose, or when…