What is storm-polish?

A finishing step for the STORM research-and-writing process. It adds a summary or introduction, removes repeated paragraphs, and checks that inline citations match the reference list.

Use it to polish an existing article, create its summary section, remove repetition, and verify citation consistency.

It catches duplicated content and broken or missing source links before a researched article is finished.

storm-polish — Skill for Claude Code by FradSer/dotclaude

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 polish

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/fradser/dotclaude/polish/github.svg)](https://agentmods.dev/skills/fradser/dotclaude/polish)

Your own site

<a href="https://agentmods.dev/skills/fradser/dotclaude/polish"><img src="https://agentmods.dev/badge/skills/fradser/dotclaude/polish/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/fradser/dotclaude/polish"><img src="https://agentmods.dev/badge/skills/fradser/dotclaude/polish.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 576 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.

Model	Per session	Once invoked
Fable 5.1	$0.00059	$0.00576
Opus 5.5	$0.00024	$0.00230
Sonnet 5.5	$0.00012	$0.00115
Haiku 4.5	$0.00006	$0.00058

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

Security

Grade A, and why

storm-polish 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/polish/SKILL.md · 35 lines

What it actually says

/storm:polish

Phase 4 of the STORM pipeline. Adds a summary/intro section, removes duplicate content across sections, and verifies every inline [n] citation resolves to a References entry and vice versa.

CRITICAL: Prerequisites

Load storm-engine via the Skill tool.
article.md MUST exist (phase 3 complete). If absent, stop and instruct the user to run /storm:write first.

Completion Contract

This phase is complete iff article-polished.md exists. If --force is not set and it exists, skip and exit early.

Procedure

Resolve output dir.
Read article.md, outline.md, and research/sources.json.
Summary section — if outline.md had an "Introduction" or "Summary" placeholder, write a summary section synthesizing the article's main points (1-2 paragraphs). Do not introduce new claims or citations not already in the body.
Duplicate removal (default on; --remove-duplicate is explicit but the behavior is the default) — detect near-duplicate paragraphs across sections and remove the later occurrence, keeping the one in the more topically-appropriate section.
Citation integrity — build the set of [n] keys present in the body. Append a ## References section listing exactly those sources, numbered to match, each as n. title — url (accessed YYYY-MM-DD). Drop any [n] in the body that has no source (replace with ). Drop any source not cited (do not list uncited sources in References).
Write article-polished.md.
Update run-config.json: phases.polish = "completed", final word count, source count, any integrity warnings.

Output

Report: final word count, number of cited sources, number of duplicate paragraphs removed, any integrity warnings (missing sources / TODO sections), and the absolute path to article-polished.md.

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.

22d ago First seen · 35 lines · 59 tokens per session scan A 8a8a5db0bf63

Subscribe to this mod's changes

storm-polish is a skill published in the GitHub repository FradSer/dotclaude (593 stars, last pushed 7d ago), licensed MIT. It adds 59 tokens to every session and 576 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-24.

Research Writing and docs claude

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