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 agentmods add skills/webhook-co/webhook/brainstormingnpx skills add webhook-co/webhook --skill brainstorminggit clone --depth 1 https://github.com/webhook-co/webhookWhat 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 | $0.00052 | $0.00507 |
| Opus 5 | $0.00026 | $0.00253 |
| Sonnet 5 | $0.00010 | $0.00101 |
| Haiku 4.5 | $0.00005 | $0.00051 |
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 yesterday.
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.
What it actually says
Brainstorming
Refine the requirement before touching code. Most wasted work comes from building the wrong thing confidently — this skill front-loads the questions so the design that follows is aimed correctly.
Method — ask before you build
Work as a Socratic partner, not an order-taker. One focused question at a time; build on the answers.
- Restate the goal in one line: who is this for, which surface(s) (CLI/API/web/MCP), and what outcome do they actually want? Confirm the restatement before going further.
- Probe the why. What problem does this solve? What happens if we don't build it? What does success look like, concretely?
- Surface constraints and unknowns. Tenant/auth context, data sensitivity (PII/PHI, raw payloads), parity expectations across surfaces, performance and ordering needs, and the non-negotiables that apply (compliance-by-design, Standard-Webhooks-native, private-by-default, open-core boundary).
- Explore alternatives. Name two or three approaches with their tradeoffs; have a point of view on which is right and why. Don't just enumerate.
- Pin down scope. What's explicitly in, what's out, and what's deferred. Identify the riskiest assumption to validate first.
Output
A short, agreed brief: the problem, the chosen direction (with the tradeoff that decided it), the
constraints it must respect, the surfaces it touches, and the open questions still needing a human
answer. This brief is the input to /feature-dev or an implementation plan — don't start coding from
an unconfirmed brief.
Guardrails
- Stop and ask when the ask is ambiguous, conflicts with a non-negotiable, or would need human UX judgment — don't paper over it with assumptions.
- Keep parity in view: a capability on one surface is considered for all four.
- Public-safe: no pricing numbers, cost figures, or business strategy in the brief.
Progressive disclosure
Keep question banks and a brief template in references/.
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.
- yesterday First seen · 44 lines · 52 tokens per session scan A 609c8e94cf8a
brainstorming is a skill published in the GitHub repository webhook-co/webhook (0 stars, last pushed 7d ago), licensed Apache-2.0. It adds 52 tokens to every session and 507 once invoked, about $0.0003 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
update-saasmail
Sync the local saasmail repo with the latest upstream changes from https://github.com/choyiny/saasmail. Use this skill whenever the user wants to update saasmail, pull upstream changes, sync with upstream, rebase on upstream, get the latest saasmail, or says "/update-saasmail". Handles adding the upstream remote if…
story-html-publisher
Final step of the AI Storybook pipeline. Consolidates the scenes, images, and per-scene audio into ONE self-contained HTML storybook — a swipe/tap player with every image and audio clip embedded as base64 so the single file works offline and can be shared as-is. Reads {slug}scenes.json, {slug}images.json, and…
github-code-review
Comprehensive GitHub code review with AI-powered swarm coordination.
Pair Programming
AI-assisted pair programming with multiple modes (driver/navigator/switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Features automatic role switching, continuous code review, security scanning, and performance optimization with…
sparc-methodology
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration.
Skill Builder
Create new Claude Code Skills with proper YAML frontmatter, progressive disclosure structure, and complete directory organization. Use when you need to build custom skills for specific workflows, generate skill templates, or understand the Claude Skills specification.