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 rumotion/ai-agent-project-template --skill storm-researchgit clone --depth 1 https://github.com/rumotion/ai-agent-project-templateWrote 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/rumotion/ai-agent-project-template/storm-research)<a href="https://agentmods.dev/skills/rumotion/ai-agent-project-template/storm-research"><img src="https://agentmods.dev/badge/skills/rumotion/ai-agent-project-template/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.
<a href="https://agentmods.dev/skills/rumotion/ai-agent-project-template/storm-research"><img src="https://agentmods.dev/badge/skills/rumotion/ai-agent-project-template/storm-research.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.00132 | $0.02713 |
| Opus 5.5 | $0.00053 | $0.01085 |
| Sonnet 5.5 | $0.00026 | $0.00543 |
| Haiku 4.5 | $0.00013 | $0.00271 |
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 13d 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.
This is a copy
100% identical to storm-research — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Storm Research
What this does
Turns one topic into a verified, multi-perspective HTML briefing. It simulates five expert lenses on the topic, maps where they contradict each other, synthesizes everything into a single self-contained HTML report, then adversarially peer-reviews its own output and verifies every citation against its primary source before delivering. The output is one HTML file with no blind spots and no unchecked claims.
Run the full pipeline end to end. Do not shortcut a phase. This is heavier than a quick web lookup; that is the point.
Portability
This skill is self-contained. It depends only on built-in Claude Code tools (the Agent tool with the built-in general-purpose agent, Write, and web search/fetch used inside those agents) plus report_template.html in this same folder. No external scripts, APIs, paid services, or other skills are required. Drop the folder into any .claude/skills/ directory and it works.
Phase 0: Scope the topic
- If
$ARGUMENTShas the topic, use it. Otherwise ask what to research. - State your interpretation of the topic in one line and proceed. Only ask a clarifying question if the topic is genuinely ambiguous in a way that changes the research. Default to proceeding.
- Identify the reader's role so the actionable section can target it. Infer it from the topic and any stated context; if unclear, ask in one line, or default to "a practitioner or decision-maker in this field."
- Derive a kebab-case
topic-slugfrom the topic for the filename. - Tell the user the pipeline is running (5 lenses, then verify). One line.
Phase 1: Five expert lenses (parallel agents)
Spawn five general-purpose agents in a single message so they run concurrently. Each gets the SAME topic framing plus its own lens. Use these exact prompts, substituting {TOPIC} and a one-line {TOPIC_FRAME} (your Phase 0 interpretation):
1. THE PRACTITIONER — You are THE PRACTITIONER for: {TOPIC} ({TOPIC_FRAME}). You work with this daily. Do real web research (prioritize recent sources, case studies, practitioner threads, operator data). Surface the GAP between what hands-on operators know and what academics/pundits miss, and the practical realities (workflow friction, what actually works, where it breaks) that get ignored. Return EXACTLY: 1) CORE POSITION in 2 sentences. 2) STRONGEST EVIDENCE, 3-5 bullets each with a concrete data point/case/named source + URL. 3) THE ONE THING only a practitioner would say. Cite real sources with URLs. Under 400 words.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 13d ago First seen · 101 lines · 0 tokens per session scan A a7242c030b2a
storm-research is a skill published in the GitHub repository rumotion/ai-agent-project-template (1 stars, last pushed 13d ago), licensed MIT. It adds 132 tokens to every session and 2,713 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to storm-research, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
saas-builder
Clone, verify, map, and build on top of ixartz/SaaS-Boilerplate for a user's SaaS idea. Use when a user wants to reuse SaaS Boilerplate, evaluate how their product fits it, or build product-specific pages, database schema, roles, permissions, MVP features, and launch scope on top of the boilerplate.
dashboard-builder
Build self-contained interactive HTML dashboards with charts, filters, and tables. Generates a single browser-openable file — no server or dependencies required.
bionic-decision-engine
Unified mathematical arbitrator for all resource allocation decisions — money, time, energy, relationships. Absorbs 46 decision protocols + 24 strategy protocols into one dense engine.
trading-risk-gate
Unified pre-trade safety gate: Ruin check (Law #1), ergodicity audit, and win-rate dominance validation. Absorbs: ergodicity-check, law-of-ruin, win-rate-dominance.
skill-creator-primer
You MUST load this skill before the skill-creator skill AND before making ANY change to, or conducting a review of ANY Agent Skill. Triggers include creating, editing, reviewing, or contributing to any part of an Agent Skill (description, frontmatter, body, references, scripts, trigger evals, conflicts, etc).
database-patterns
DB schema design and query tuning: normalization, indexing, N+1, transactions, EXPLAIN. Triggers: schema, index, slow query, N+1, PostgreSQL, MySQL, EXPLAIN, deadlock, query plan.