agentmods.dev

storm-generate

storm-generate is a skill for Claude Code from FradSer/dotclaude. It costs 74 tokens per session (921 once invoked), scanned A, original, MIT.

An end-to-end tool for the STORM process, which researches a topic, builds an outline, writes the article, and polishes the result. It can use web, local, or connected research sources and save the work as files.

In plain words
What is it for?
Use it to generate a researched, outlined, cited, and polished long-form or Wikipedia-style article from a topic, optionally grounded in local documents.
Why use it?
It removes the need to run each research and writing phase by hand while preserving the results so completed phases can be reused.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions subagents; names the AskUserQuestion tool.

Part of the storm plugin — 5 skills, 1 agent shipped together

not rated 593repo 7d ago A scan 74 tokens original MIT

Good fit Use it to generate a researched, outlined, cited, and polished long-form or Wikipedia-style article from a topic, optionally grounded in local documents.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fradser/dotclaude/generate
View source ↗ FradSer/dotclaude dotclaude.frad.me
Install

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.

Any agent
npx skills add FradSer/dotclaude --skill generate
Clone the repo
git clone --depth 1 https://github.com/FradSer/dotclaude

Made for: Claude Code.

Or install storm, the plugin that ships this one along with the rest of its 5 skills, 1 agent.

Wrote 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.

agentmods badge for storm-generate

README.md
[![agentmods](https://agentmods.dev/badge/skills/fradser/dotclaude/generate/github.svg)](https://agentmods.dev/skills/fradser/dotclaude/generate)
Your own site
<a href="https://agentmods.dev/skills/fradser/dotclaude/generate"><img src="https://agentmods.dev/badge/skills/fradser/dotclaude/generate/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.

agentmods 80×15 button for storm-generate

Your own site · 80×15
<a href="https://agentmods.dev/skills/fradser/dotclaude/generate"><img src="https://agentmods.dev/badge/skills/fradser/dotclaude/generate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 921 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00074 $0.00921
Opus 5.5 $0.00030 $0.00368
Sonnet 5.5 $0.00015 $0.00184
Haiku 4.5 $0.00007 $0.00092

Measured 22d ago against content hash 76cf3f978b26, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

storm-generate 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 22d 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.

storm/skills/generate/SKILL.md · 56 lines

How it starts

The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/storm:generate

End-to-end STORM article generation. Runs all four phases in sequence, skipping any phase whose artifact already exists (unless --force).

CRITICAL: Load Engine First

Load the storm-engine skill via the Skill tool before doing anything else. It defines the artifact layout, stage-gating contract, citation hygiene, and retrieval fallback that this orchestration depends on. Do not improvise these.

Arguments

  • <topic> (required) — the subject of the article.
  • --max-perspective N (default 3) — number of personas to discover.
  • --max-turns N (default 3) — max Q&A turns per persona.
  • --output-dir PATH — explicit output location. Mutually exclusive with --save.
  • --save — persist to docs/storm/<slug>/ instead of a temp dir.
  • --docs DIR — ground on local documents in addition to (or, with --docs-only, instead of) the web.
  • --force — re-run all phases even if artifacts exist.
  • --retriever mcp|web|local — override retrieval source (default: mcp with fallback).

Procedure

  1. Parse arguments; if no topic, invoke AskUserQuestion to request one.
  2. Derive <slug> and resolve <output_dir> per the engine contract. Create the directory.
  3. Write run-config.json with a snapshot of all parameters. Stamp started_at using date -u +%Y-%m-%dT%H:%M:%SZ (the only place a timestamp is generated).
  4. For each phase in order — research, outline, write, polish: a. Check the phase's completion artifact (per engine contract). b. If complete and not --force: mark phases.<name>: "skipped" in run-config.json, log "Skipping (artifact present)". c. Otherwise: invoke the corresponding /storm:<phase> skill via the Skill tool, passing the resolved output dir and run parameters. After it returns, verify its artifact and mark phases.<name>: "completed" (or "failed" with the error).
  5. After all phases, read article-polished.md and print a summary: topic, word count, number of sources cited, number of sections, and the absolute path to the final article.
  6. If the run used a temporary directory, surface its absolute path prominently so the user can rescue artifacts.

Read the full file on GitHub · 56 lines

Changes

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.

  1. 22d ago First seen · 56 lines · 74 tokens per session scan A 76cf3f978b26

Subscribe to this mod's changes

storm-generate is a skill published in the GitHub repository FradSer/dotclaude (593 stars, last pushed 7d ago), licensed MIT. It adds 74 tokens to every session and 921 once invoked, about $0.0003 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-24.

ResearchWriting and docsclaude
Related

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens