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 anton-abyzov/specweave --skill sw-brainstormgit clone --depth 1 https://github.com/anton-abyzov/specweaveWrote 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/anton-abyzov/specweave/sw-brainstorm)<a href="https://agentmods.dev/skills/anton-abyzov/specweave/sw-brainstorm"><img src="https://agentmods.dev/badge/skills/anton-abyzov/specweave/sw-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/anton-abyzov/specweave/sw-brainstorm"><img src="https://agentmods.dev/badge/skills/anton-abyzov/specweave/sw-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.00039 | $0.00582 |
| Opus 5.5 | $0.00016 | $0.00233 |
| Sonnet 5.5 | $0.00008 | $0.00116 |
| Haiku 4.5 | $0.00004 | $0.00058 |
Grade A, and why
sw-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 20d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sw-brainstorm: diverge, converge, pick
Decides which thing to spec; it never replaces the spec. Hand the winner to sw-increment.
Depth
| Depth | Options | Output |
|---|---|---|
quick (default for a narrow question) |
3 | a table and a pick, in the conversation |
standard |
4 to 5 | table, trade-offs, reports/brainstorm.md if an increment exists |
deep |
5 to 7, including "do nothing" and one contrarian | written doc, rejected alternatives, risks |
Steps
- Frame. One sentence: the decision and what makes an answer good. Write 3 to 5 criteria first (cost, time to ship, blast radius, reversibility, who maintains it). Choosing criteria after seeing the options is how bias gets in.
- Diverge. Generate before judging, and force variety: the obvious one, the cheap one (80% for 20%), buy instead of build, do nothing or defer (with its cost), and one that inverts an assumption everyone makes. Name each in 3 to 6 words.
- Converge. One table, option by criteria, with a "kills it if" per option. Then a short paragraph per survivor: how it works, what it costs, what breaks.
- Pick. The recommendation, the runner-up, and the one fact that would flip it. If the honest answer is "we need data", name the experiment.
- Hand off.
specweave create-increment "<the pick>"(sw-increment) and paste the rejected alternatives into its Approach section.
Contested decisions
Run three lenses over the same options: advocate (strongest case for), critic (how each fails in production), pragmatist (what ships this week). If your tool supports subagents, run them in parallel; otherwise do three labelled passes in sequence. Merge.
Rules
- Never grade an option while still generating options; give each the same scrutiny.
- Tables and short paragraphs, not essays.
- If the user already knows what they want, skip to sw-increment and say why.
Manual path (no CLI)
Nothing here needs the CLI; create the increment folder by hand as sw-increment describes.
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.
- 20d ago First seen · 49 lines · 39 tokens per session scan A 07c65fb10aab
sw-brainstorm is a skill published in the GitHub repository anton-abyzov/specweave (165 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 582 once invoked, about $0.0002 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-09-26.
Other skills, from other repositories
bench
GEML is plain text. Every structured thing is one typed block.
project-init
A project-initialization skill that creates a standard starting structure for documentation or software projects. It can add files such as README.md, source, documentation, tests, and project rules.
write-readme
Generates or updates a README.md for a project or package. Reads the source code to understand the project and produces a clear, accurate README following the project's conventions. Invoked when the user asks to write, update, or generate a README.
write-changelog
Generates a CHANGELOG.md entry for a release by summarizing git commits since the last tag. Groups changes by type: Added, Changed, Fixed, Removed. Follows Keep a Changelog format (https://keepachangelog.com). Invoked when the user asks to update the changelog, write release notes, or prepare a release.
doc-summarize
A document-summary workflow for Markdown, plain text, and code documents. It extracts the main points, structure, data, and practical recommendations.
doc-translation
A tool for translating technical documentation while preserving its Markdown structure. Markdown is a plain-text format for headings, lists, links, tables, and code blocks.