revise

revise is a skill for Claude Code from helderberto/agent-skills. It costs 68 tokens per session (724 once invoked), scanned A, original, MIT.

A structured editor for improving the organization and clarity of article drafts. It examines how ideas depend on one another before rewriting the piece.

In plain words
What is it for?
Use it to revise an article by clarifying its audience and purpose, mapping the structure, and strengthening the flow and argument.
Why use it?
It helps fix weak introductions, missing explanations, repeated points, and sections that appear before the reader has the needed context.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: names the AskUserQuestion tool.

Part of the hb plugin — 40 skills, 6 agents shipped together

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.

agentmods
npx agentmods add skills/helderberto/agent-skills/revise
Any agent
npx skills add helderberto/agent-skills --skill revise
Clone the repo
git clone --depth 1 https://github.com/helderberto/agent-skills

Made for: Claude Code.

Or install hb, the plugin that ships this one along with the rest of its 40 skills, 6 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 revise

README.md
[![agentmods](https://agentmods.dev/badge/skills/helderberto/agent-skills/revise.svg)](https://agentmods.dev/skills/helderberto/agent-skills/revise)
Your own site
<a href="https://agentmods.dev/skills/helderberto/agent-skills/revise"><img src="https://agentmods.dev/badge/skills/helderberto/agent-skills/revise.svg" alt="Measured on agentmods" height="20"></a>
Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 724 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00068 $0.00724
Opus 5 $0.00034 $0.00362
Sonnet 5 $0.00014 $0.00145
Haiku 4.5 $0.00007 $0.00072

Measured 6d ago against content hash 7661ac84b23e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

revise 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 6d 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.

skills/revise/SKILL.md · 70 lines

How it starts

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

Revise

Structurally edit an article draft through an interactive, section-by-section process. Unlike prose-fix (cosmetic polish), this skill rewrites for clarity, flow, and argument strength.

Step 1 — Understand Context

Before editing, ask the user (skip questions they already answered). Use AskUserQuestion when available; otherwise ask directly:

  1. Audience: "Who is the target audience?" — Options: "Beginners", "Experienced developers", "General tech readers"
  2. Venue: "Where will this be published?" — Options: "Blog post", "Newsletter", "Documentation"
  3. Takeaway: "What is the one thing the reader should remember?" — ask separately as text (too specific for predefined options)

Step 2 — Analyze Structure

Read the full article. Map the sections as an information DAG — each concept depends on prior concepts. Identify:

  • Dependency violations: concept used before it is introduced
  • Redundant sections: same point made twice in different places
  • Missing sections: logical gaps the reader needs bridged
  • Weak intro: does the first paragraph hook and set expectations?
  • Weak conclusion: does it reinforce the one takeaway?

Present the current section outline and a proposed reordering. Wait for user confirmation before proceeding.

Step 3 — Rewrite Section by Section

For each section, in order:

  1. Lead with the point — first sentence states what the section proves or teaches
  2. Max 240 characters per paragraph — split longer paragraphs
  3. Cut ruthlessly — remove sentences that don't serve the section's point
  4. Smooth transitions — each section's opening should connect to the previous section's conclusion
  5. Show, don't tell — prefer concrete examples over abstract claims

Edit the file in place, one section at a time.

Step 4 — Final Check

After all sections are revised:

  1. Re-read the full article for flow
  2. Verify the intro promises what the article delivers
  3. Verify the conclusion reinforces the one takeaway
  4. Check that no concept is used before it is introduced
  5. Report a summary of structural changes made

Read the full file on GitHub · 70 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. 6d ago First seen · 70 lines · 68 tokens per session scan A 7661ac84b23e

Subscribe to this mod's changes

revise is a skill published in the GitHub repository helderberto/agent-skills (14 stars, last pushed 4d ago), licensed MIT. It adds 68 tokens to every session and 724 once invoked, about $0.0003 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-30.

Related

Other skills, from other repositories

case-interview-practice

Interactive consulting case interview practice with structured frameworks, feedback mechanisms, and progressive difficulty. Use when preparing for management consulting interviews, case competitions, or business problem-solving exercises.

travisjneuman/.claude · 39 tokens

finance

Financial analysis expertise for financial modeling (DCF, LBO, M&A), valuation, financial statement analysis, capital allocation, treasury management, and corporate finance decisions. Use when building financial models, analyzing statements, or making investment decisions.

travisjneuman/.claude · 48 tokens

i18n-localization

Internationalization and localization for global applications. Use when adding multi-language support, handling regional formats, or preparing apps for global markets.

travisjneuman/.claude · 32 tokens

content-repurposer

Adapt content across platforms with tone/format shifting — blog to social, long to short, text to visual outline. Use when repurposing content for different channels, audiences, or formats.

travisjneuman/.claude · 43 tokens

impact-report-writer

Nonprofit/NGO impact report generation with data visualization suggestions, outcome metrics, narrative structure, and program data presentation. Use when writing impact reports, annual reports, or program evaluation summaries.

travisjneuman/.claude · 43 tokens

investment-memo-generator

Investment memo creation combining financial analysis, document generation, and structured templates. Use when creating investment memos, pitch decks, deal summaries, or investment committee materials.

travisjneuman/.claude · 37 tokens