storm-research

storm-research is a skill for Claude Code from HirogaKatageri/hirokata. It costs 141 tokens per session (1,968 once invoked), scanned A, original, MIT.

A workflow for deep research that examines a topic through five different expert viewpoints, combines their findings, and reviews the result.

In plain words
What is it for?
Producing broad, cited research briefings on complex topics through practitioner, skeptic, economist, historian, and academic analyses.
Why use it?
It reduces the risk of relying on one narrow perspective or overlooking disagreements, gaps, and weaknesses in the evidence.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: mentions subagents.

Part of the research plugin — 4 skills, 8 agents shipped together

Good fit Producing broad, cited research briefings on complex topics through practitioner, skeptic, economist, historian, and academic analyses.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hirogakatageri/hirokata/storm-research
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 HirogaKatageri/hirokata --skill storm-research
Clone the repo
git clone --depth 1 https://github.com/HirogaKatageri/hirokata

Made for: Claude Code.

Or install research, the plugin that ships this one along with the rest of its 4 skills, 8 agents.

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-research

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/hirogakatageri/hirokata/storm-research"><img src="https://agentmods.dev/badge/skills/hirogakatageri/hirokata/storm-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 141 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,968 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.00141 $0.01968
Opus 5 $0.00071 $0.00984
Sonnet 5 $0.00028 $0.00394
Haiku 4.5 $0.00014 $0.00197

Measured 11d ago against content hash 5b99db72e9de, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

storm-research 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 11d 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.

plugins/research/skills/storm-research/SKILL.md · 165 lines

How it starts

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

STORM Research — Multi-Perspective Deep Research Orchestrator

Run the full STORM pipeline on a topic. One prompt asks one question and returns the majority view — the surface. STORM asks the same topic from five independent expert lenses, maps where they fight, synthesizes a briefing no single expert could write, then red-teams its own output. In Stanford's peer-reviewed testing, multi-perspective articles were ~25% more organized and ~10% broader than single-pass research. This skill operationalizes that with dedicated sub-agents so the heavy reading happens off the main context window.

The Pipeline

Topic
 └─ Phase 1  FAN-OUT (parallel): practitioner · skeptic · economist · historian · academic
 └─ Phase 2  CONTRADICTION MAP: contradiction-mapper reads all 5 → finds clashes/agreement/gaps
 └─ Phase 3  SYNTHESIS: synthesizer reads 5 + map → cited research briefing
 └─ Phase 4  PEER REVIEW: peer-reviewer audits the briefing → reliability grade + fixes
 └─ Present consolidated result to the user

Workflow

Step 0 — Scope the Topic

  1. Get the topic. If the user supplied one (storm research <topic>), use it. If it's vague or sprawling (e.g. "AI", "the economy"), ask one sharpening question to narrow it — a tight topic produces a far better briefing than a broad one.
  2. Capture the audience and angle if offered (deciding / investing / writing / presenting / learning). It tunes the synthesizer's recommendations. Don't interrogate — one optional ask.
  3. Derive a slug (lowercase, hyphenated, canonical: e.g. lab-grown-meat-viability).
  4. Set the workspace: .storm/{slug}/. Create it: mkdir -p .storm/{slug}.

Step 0.5 — Tune the Panel (optional, powerful)

The five default personas fit most topics. For some topics, a swap sharpens the analysis — e.g. add a Clinician for a medical topic, a Regulator for a policy topic, an End User for a product topic. If a swap clearly helps, mention it to the user and spawn the extra persona with the Task tool using the same output contract as the built-in agents (worldview + owned bias + evidence-gathering + structured file with sources). Keep the panel at 5–6; more dilutes. Default to the standard five if unsure.

Read the full file on GitHub · 165 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. 11d ago First seen · 165 lines · 141 tokens per session scan A 5b99db72e9de

Subscribe to this mod's changes

storm-research is a skill published in the GitHub repository HirogaKatageri/hirokata (5 stars, last pushed 2d ago), licensed MIT. It adds 141 tokens to every session and 1,968 once invoked, about $0.0007 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.

Related

Other skills, from other repositories

unslop

Humanize LLM output so it reads like a careful human wrote it. Subtracts AI-isms (sycophancy, tricolons, em-dash overuse, "delve"/"tapestry"/"testament", hedging stacks, tidy five-paragraph shapes), engineers burstiness and calibrated uncertainty, and preserves technical accuracy. Supports intensity levels: subtle…

MohamedAbdallah-14/unslop · 146 tokens

unslop-file

Humanize natural-language memory files (CLAUDE.md, todos, preferences, docs) by removing AI-isms and adding burstiness while preserving every code block, URL, path, command, and heading exactly. Two modes: --deterministic (fast, regex-based, no API) and LLM (default, calls Claude for rewrite). Humanized version…

MohamedAbdallah-14/unslop · 107 tokens

unslop-commit

Rewrites commit messages so they sound like a careful human engineer wrote them. Strips AI/marketing slop ("comprehensive solution", "robust implementation", "leverage", "enhance", "seamlessly", "This commit..."). Keeps Conventional Commits format. Subject ≤72 chars (aim ≤50), imperative mood. Body only when "why"…

MohamedAbdallah-14/unslop · 139 tokens

unslop-help

Quick-reference card for unslop modes, sub-skills, and slash commands. One-shot display, not a persistent mode. Trigger: /unslop-help, "unslop help", "what unslop commands", "how do I use unslop".

MohamedAbdallah-14/unslop · 55 tokens

simulator-charts

Simulator.Company chart and dashboard specialist. Use when the user wants to create, configure, or query charts (line, bar, area), dashboards, or financial time-series visualisations on a graph layer. Trigger on any of these intents: — Creating: "create chart", "add chart", "create dashboard", "add dashboard", "build…

corezoid/simulator-ai-plugin · 185 tokens

simulator-init

Simulator.Company environment setup specialist. Use when the user wants to connect to Simulator.Company, set up credentials, authenticate, configure the workspace, or start working with Simulator for the first time. Activate when the user says "init", "setup", "connect to simulator", "login to simulator", "configure…

corezoid/simulator-ai-plugin · 77 tokens