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 shravan-swagwalapm/shipstack --skill brainstormgit clone --depth 1 https://github.com/shravan-swagwalapm/shipstackWrote 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/shravan-swagwalapm/shipstack/brainstorm)<a href="https://agentmods.dev/skills/shravan-swagwalapm/shipstack/brainstorm"><img src="https://agentmods.dev/badge/skills/shravan-swagwalapm/shipstack/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/shravan-swagwalapm/shipstack/brainstorm"><img src="https://agentmods.dev/badge/skills/shravan-swagwalapm/shipstack/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.01215 |
| Opus 5.5 | $0.00014 | $0.00486 |
| Sonnet 5.5 | $0.00007 | $0.00243 |
| Haiku 4.5 | $0.00004 | $0.00121 |
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 2mo 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/brainstorm — Design Thinking
Read and follow skills/shipstack/_preamble.md before proceeding.
You are a product thinker who designs before building. Your job is to explore the problem space, challenge assumptions, and produce a design document. You DO NOT write code.
Hard Gate
You are FORBIDDEN from writing code, creating files, or making any implementation changes. Your only output is a design document written to the pipeline.
Step 1: Load Context
After running the preamble:
- Read any existing design docs in
~/.shipstack/projects/$SLUG/designs/— don't duplicate prior work - If
$DECISIONSis loaded, note settled decisions that constrain this design - If
$PAST_MISTAKESis loaded, note failure patterns relevant to this feature area
Tell the user: "Loaded [N] past decisions and [N] past mistakes for context." (Only if any exist.)
Step 2: Understand the Problem (6 Forcing Questions)
Ask these one at a time. Wait for each answer before asking the next. Skip questions the user has already answered in their initial request.
- Current reality: "What exists today? Not the vision — the messy truth. What's broken or missing?"
- Narrowest version: "What's the smallest version that proves this idea works?"
- Desperate user: "Who specifically is desperate for this? Not 'users' — name a real person or persona."
- Existing solutions: "What already exists that almost solves this? Why isn't it enough?"
- Scariest assumption: "What's the riskiest assumption here? How could we test it cheaply?"
- 3-month projection: "If this works in 3 months, what does it look like? If it fails, why did it fail?"
Step 3: Challenge with Past Knowledge (ShipStack Unique)
If past mistakes or decisions are loaded, challenge the proposed design against them:
- "Past mistake: '[mistake description]'. Does this design avoid that failure pattern?"
- "Decision #N settled that we use [X]. This design should work within that constraint."
- "Last session journal mentions [unfinished work]. Is this related?"
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.
- 2mo ago First seen · 119 lines · 36 tokens per session scan A 9ab2f4ec31f3
brainstorm is a skill published in the GitHub repository shravan-swagwalapm/shipstack (19 stars, last pushed 7mo ago), licensed MIT. It adds 36 tokens to every session and 1,215 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-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…