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 Heyvhuang/ship-faster --skill workflow-brainstormgit clone --depth 1 https://github.com/Heyvhuang/ship-fasterWrote 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/heyvhuang/ship-faster/workflow-brainstorm)<a href="https://agentmods.dev/skills/heyvhuang/ship-faster/workflow-brainstorm"><img src="https://agentmods.dev/badge/skills/heyvhuang/ship-faster/workflow-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/heyvhuang/ship-faster/workflow-brainstorm"><img src="https://agentmods.dev/badge/skills/heyvhuang/ship-faster/workflow-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.00086 | $0.00853 |
| Opus 5 | $0.00043 | $0.00426 |
| Sonnet 5 | $0.00017 | $0.00171 |
| Haiku 4.5 | $0.00009 | $0.00085 |
Grade A, and why
workflow-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 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorming Ideas Into Designs
Goal
Transform "vague ideas/requirements" into actionable designs and specifications, producing reusable file artifacts (rather than just staying in chat).
Key requirement: Ask only one question at a time. If a topic is complex, break it into multiple rounds of Q&A—don't throw out a checklist all at once.
Core Process (Must Follow)
0) Check Project Context First (Required When Repo Exists)
Before asking questions, quickly check:
- Key documentation:
README.md,docs/,design-system.md(if exists) - Tech stack and constraints:
package.json/Cargo.toml/pyproject.tomletc. - Structure overview: top-level directories, main modules
- Recent changes:
git log -n 10 --oneline(if it's a git repo)
Output a very brief context summary: what you observed + possible constraint points (don't start designing yet).
1) Understand the Idea (One Question at a Time)
Goal is to gather the minimum information set (purpose / constraints / success criteria).
Rules:
- Each message asks 1 question only
- Prefer multiple choice (reduce user's cognitive load), use open questions only when necessary
- Ask direction-determining questions first (goals/success criteria/non-goals), then details
2) Explore Solutions (2-3 Options + Trade-offs)
After you understand the requirements:
- Provide 2-3 options (A/B/C)
- Explain trade-offs for each (complexity/risk/iteration speed/long-term cost)
- Give your recommended option first, then explain why
3) Output Design (200-300 Word Segments + Confirm Each)
When you're confident you understand what needs to be done, start outputting the design spec.
Requirements:
- Output in segments (~200-300 words each)
- Ask for confirmation at the end of each segment: e.g., "Does this look good?"
- Design should at least cover:
- Architecture and module boundaries
- Core data flow (input → processing → output)
- Error handling and edge cases
- Testing and validation strategy (minimum viable set)
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 · 82 lines · 86 tokens per session scan A 77dbfd818443
workflow-brainstorm is a skill published in the GitHub repository Heyvhuang/ship-faster (339 stars, last pushed 25d ago), licensed MIT. It adds 86 tokens to every session and 853 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…