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 byerlikaya/claude-starter-kit --skill brainstormgit clone --depth 1 https://github.com/byerlikaya/claude-starter-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/byerlikaya/claude-starter-kit/brainstorm)<a href="https://agentmods.dev/skills/byerlikaya/claude-starter-kit/brainstorm"><img src="https://agentmods.dev/badge/skills/byerlikaya/claude-starter-kit/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/byerlikaya/claude-starter-kit/brainstorm"><img src="https://agentmods.dev/badge/skills/byerlikaya/claude-starter-kit/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.00049 | $0.00759 |
| Opus 5 | $0.00024 | $0.00380 |
| Sonnet 5 | $0.00010 | $0.00152 |
| Haiku 4.5 | $0.00005 | $0.00076 |
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 10d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorm — diverge before you converge
Trigger phrases: "brainstorm", "explore options", "not sure what we want", "help me scope", "ideate"
When
The ask is under-defined: the goal, the users, or the shape of the solution aren't clear yet, so jumping
straight to spec-planning would just plan the wrong thing. This is the front-end of planning, not a
replacement — brainstorm diverges (widens the option space), spec-planning converges (breaks the chosen
option into tasks). If scope is already clear, skip this and go straight to [[spec-planning]].
The loop
- Frame the real problem — restate the request as the underlying need in one sentence ("the user wants X so that Y"). Separate the stated solution from the goal; often the solution is negotiable, the goal isn't.
- Diverge — generate distinct directions. Produce 2–4 genuinely different approaches, not variations of one. For each: the core idea, who it serves, the main trade-off. Include a deliberately cheap/minimal option (fight gold-plating early).
- Surface the unknowns — list assumptions and open questions that would change the answer. Mark which are blocking (must resolve before planning) vs. deferrable.
- Converge — ask, don't guess. Present the directions as explicit numbered options and let the user choose (CLAUDE.md discipline: a decision point = multiple choice, never a prose either/or). Record the chosen direction + the rejected ones with the one-line reason they lost.
- Hand off. The chosen direction + resolved constraints flow into
spec-planning; a lasting architectural choice made here is recorded with [[adr]].
Guardrails
- Bounded, not open-ended. Divergence has a stop: 2–4 options, then converge. Endless ideation with no decision is the failure mode, not thoroughness.
- No premature convergence either. Don't collapse to the first idea to look decisive — the point is that the option space was actually explored before a direction was picked.
- Evidence over invention. Read the existing code/data and state assumptions explicitly; a plausible guess presented as fact is worse than a named unknown.
- Token discipline ([[token-budget]]): the options + the decision are a short summary to the main thread;
push a long exploration to
docs/DISCOVERY.mdand return the option headings + the choice.
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.
- 10d ago First seen · 50 lines · 49 tokens per session scan A 07d3bc34787e
brainstorm is a skill published in the GitHub repository byerlikaya/claude-starter-kit (22 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 759 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-30.
Other skills, from other repositories
security-compliance
Guides security professionals in implementing defense-in-depth security architectures, achieving compliance with industry frameworks (SOC2, ISO27001, GDPR, HIPAA), conducting threat modeling and risk assessments, managing security operations and incident response, and embedding security throughout the SDLC.
stride-analysis-patterns
Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.
review-loop
Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE. Use before claiming any behavioural change is done, and on requests like "review loop", "adversarial review", "independent review", "get this verified"…
prompts-chat
Use when searching, installing, or improving AI skills and prompts via prompts.chat or skills.sh. Triggers on skill search, prompt lookup, install skill, improve prompt, prompts.chat.
writing-fragments
Grilling session that mines the user for fragments — heterogeneous nuggets of writing (claims, vignettes, sharp sentences, half-thoughts) — and appends them to a single document as raw material for a future article. Use when the user wants to develop ideas before imposing structure, or mentions "fragments", "ideate"…
caveman-help
Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".