revision-editor

revision-editor is a skill for Claude Code, Codex from Haohaha-11/Paper-Writing. It costs 0 tokens per session (584 once invoked), scanned A, original, MIT.

A revision-planning skill that converts review reports, claim checks, and writing suggestions into specific, patch-ready edits for a research paper.

In plain words
What is it for?
Use it after peer review or a paper audit to group changes by section, protect LaTeX references and formatting, resolve conflicting edits, and prepare a revision log for approval.
Why use it?
It links each proposed change to a reported problem and separates wording changes from edits that need new evidence, citations, or experiments.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it after peer review or a paper audit to group changes by section, protect LaTeX references and formatting, resolve conflicting edits, and prepare a revision log for approval.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/haohaha-11/paper-writing/revision-editor
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 Haohaha-11/Paper-Writing --skill revision-editor
Clone the repo
git clone --depth 1 https://github.com/Haohaha-11/Paper-Writing

Made for: Claude Code, Codex.

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 revision-editor

README.md
[![agentmods](https://agentmods.dev/badge/skills/haohaha-11/paper-writing/revision-editor/github.svg)](https://agentmods.dev/skills/haohaha-11/paper-writing/revision-editor)
Your own site
<a href="https://agentmods.dev/skills/haohaha-11/paper-writing/revision-editor"><img src="https://agentmods.dev/badge/skills/haohaha-11/paper-writing/revision-editor/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 revision-editor

Your own site · 80×15
<a href="https://agentmods.dev/skills/haohaha-11/paper-writing/revision-editor"><img src="https://agentmods.dev/badge/skills/haohaha-11/paper-writing/revision-editor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 584 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.00000 $0.00584
Opus 5 $0.00000 $0.00292
Sonnet 5 $0.00000 $0.00117
Haiku 4.5 $0.00000 $0.00058

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

Security

Grade A, and why

revision-editor 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.

skills/revision-editor/SKILL.md · 98 lines

How it starts

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

Revision Editor

Purpose

Turn review reports, claim audits, and writing suggestions into a controlled revision plan with patch-ready changes. This skill is the bridge between critique and actual paper edits.

When To Use

  • After paper-redteam.
  • After real reviewer comments.
  • Before camera-ready revision.
  • When multiple skills produce overlapping suggestions.

Inputs

Required:

  • target venue;
  • current draft or section text;
  • review findings;
  • claim-evidence matrix;
  • list of required changes.

Optional:

  • rebuttal plan;
  • page budget;
  • template or anonymity constraints;
  • Git diff from prior version.

Procedure

  1. Cluster requested changes by section.
  2. Separate scientific changes from wording changes.
  3. Identify changes requiring new evidence, citations, or experiments.
  4. Create a patch plan with file/section targets.
  5. Preserve LaTeX commands, labels, refs, citations, equations, and figure/table references.
  6. Avoid conflicting edits across Abstract, Introduction, Results, and Conclusion.
  7. Produce a revision log for human approval.

Rubric

Dimension Strong Weak
Traceability Every edit maps to an issue Unmotivated rewrite
Safety LaTeX and citations preserved Broken refs/cites
Claim control Claims stay evidence-backed Stronger unsupported claims
Consistency Abstract/intro/results align Sections contradict
Review usefulness Prioritizes decision impact Cosmetic edits first

Venue Adaptation

  • ICLR/NeurIPS/ICML: preserve limitations/reproducibility and update checklist-sensitive text.
  • CVPR/ECCV: preserve figure references, supplement anonymity, and visual evidence.
  • AAAI: ensure all text remains author-owned and policy-compliant.
  • TMI: preserve page-count-sensitive references, clinical caveats, and privacy/IRB language.
  • arXiv: convert anonymous review text to public version where appropriate.

Output Contract

Return:

Revision plan:
Section-by-section changes:
Evidence/citation dependencies:
Patch suggestions:
Consistency checks:
Changes requiring human approval:
Residual risks:

Read the full file on GitHub · 98 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 · 98 lines · 0 tokens per session scan A fd03ff43db85

Subscribe to this mod's changes

revision-editor is a skill published in the GitHub repository Haohaha-11/Paper-Writing (3 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 584 tokens. 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

systematic-debugging

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

obra/superpowers · 21 tokens

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

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

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

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens