revision-letter

revision-letter is a skill for Claude Code from TaewoooPark/MagLab. It costs 68 tokens per session (847 once invoked), scanned A, original, MIT.

A workflow for writing a point-by-point response to journal peer reviewers during manuscript resubmission. It quotes each reviewer comment, drafts a reply, and marks where changes should be made.

In plain words
What is it for?
Preparing a review-response letter from a journal decision, reviewer comments, author notes, and manuscript context, with factual claims tied to a DOI or manuscript location.
Why use it?
It organizes replies while preventing the system from inventing experimental results or sending the letter automatically.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Preparing a review-response letter from a journal decision, reviewer comments, author notes, and manuscript context, with factual claims tied to a DOI or manuscript location.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/taewooopark/maglab/revision-letter
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 TaewoooPark/MagLab --skill revision-letter
Clone the repo
git clone --depth 1 https://github.com/TaewoooPark/MagLab

Made for: Claude Code.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/taewooopark/maglab/revision-letter"><img src="https://agentmods.dev/badge/skills/taewooopark/maglab/revision-letter.svg" alt="Reviewed on agentmods" width="80" 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 847 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.00068 $0.00847
Opus 5 $0.00034 $0.00424
Sonnet 5 $0.00014 $0.00169
Haiku 4.5 $0.00007 $0.00085

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

Security

Grade A, and why

revision-letter 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 12d 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-letter/SKILL.md · 102 lines

How it starts

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

revision-letter — Point-by-point reviewer response letter skill

Overview

This skill drafts a structured revision response letter aligned with MagLab research integrity principles (§3.3) and the Appendix C bundle comms workflow.

Core principles:

  • Every reviewer comment is quoted verbatim before the response.
  • The AI does not invent new experimental data or results — only the author can supply those.
  • All personalisation fields (editor name, page/line numbers, new data references) are marked [FILL] for the author to complete.
  • Output always begins with HUMAN REVIEW REQUIRED.
  • The letter is never auto-sent — it is written to a file for human review.

Agent: maglab.authoring.comms.revision_letter.RevisionLetterAgent CLI command: maglab comms revision

Inputs

Key Type Required Description
review_decision str Yes Full journal decision letter containing reviewer comments
comment_notes list[str] No Author notes per reviewer comment (leave empty to use [FILL])
tone str No formal (default) | respectful | assertive
manuscript_orig str No Original manuscript excerpt (for context)
manuscript_rev str No Revised manuscript excerpt (for context)

Output

A CommsResult with:

  • text: Full revision letter starting with HUMAN REVIEW REQUIRED.
  • fill_markers: List of [FILL] positions requiring author personalisation.
  • word_count: Approximate word count.

Letter structure

HUMAN REVIEW REQUIRED

[FILL: Dear Dr. [FILL: editor name],]

We thank the reviewers for their careful reading of our manuscript.
Below we address each comment point by point.

---
Reviewer 1, Comment 1:
> [verbatim comment text]

Response:
[AI-drafted response based on author notes or [FILL]]

Change location: [FILL: page/line in revised manuscript]

---
[... additional comments ...]

Sincerely,
[FILL: Corresponding author name]

Workflow

Read the full file on GitHub · 102 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. 12d ago First seen · 102 lines · 68 tokens per session scan A 9a016986da01

Subscribe to this mod's changes

revision-letter is a skill published in the GitHub repository TaewoooPark/MagLab (11 stars, last pushed 1mo ago), licensed MIT. It adds 68 tokens to every session and 847 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.