agentmods.dev

address-reviewer-comment

address-reviewer-comment is a skill for Claude Code from Rezenders/scientific_writing_agent. It costs 40 tokens per session (1,125 once invoked), scanned A, original, Apache-2.0.

A review-response workflow for changing manuscript text in response to a specific reviewer comment. A manuscript is a paper being prepared for publication, and the workflow creates and checks possible revisions before changing the file.

In plain words
What is it for?
Use it when a reviewer targets a paragraph or section and you need candidate rewrites, scientific and consistency checks, and a refined response.
Why use it?
It helps answer reviewer concerns while preserving the surrounding meaning and consistency of the paper, without editing the file before approval.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

not rated 11repo 5mo ago A scan 40 tokens original Apache-2.0

Good fit Use it when a reviewer targets a paragraph or section and you need candidate rewrites, scientific and consistency checks, and a refined response.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rezenders/scientific_writing_agent/address-reviewer-comment
View source ↗ Rezenders/scientific_writing_agent
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 Rezenders/scientific_writing_agent --skill address-reviewer-comment
Clone the repo
git clone --depth 1 https://github.com/Rezenders/scientific_writing_agent

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 address-reviewer-comment

README.md
[![agentmods](https://agentmods.dev/badge/skills/rezenders/scientific_writing_agent/address-reviewer-comment/github.svg)](https://agentmods.dev/skills/rezenders/scientific_writing_agent/address-reviewer-comment)
Your own site
<a href="https://agentmods.dev/skills/rezenders/scientific_writing_agent/address-reviewer-comment"><img src="https://agentmods.dev/badge/skills/rezenders/scientific_writing_agent/address-reviewer-comment/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 address-reviewer-comment

Your own site · 80×15
<a href="https://agentmods.dev/skills/rezenders/scientific_writing_agent/address-reviewer-comment"><img src="https://agentmods.dev/badge/skills/rezenders/scientific_writing_agent/address-reviewer-comment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,125 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.00040 $0.01125
Opus 5 $0.00020 $0.00562
Sonnet 5 $0.00008 $0.00225
Haiku 4.5 $0.00004 $0.00112

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

Security

Grade A, and why

address-reviewer-comment 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.

.claude/skills/address-reviewer-comment/SKILL.md · 135 lines

How it starts

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

Address Reviewer Comment

Overview

Multi-agent pipeline that responds to reviewer comments by generating 2-3 candidate revision directions, subjecting full rewrites to parallel scientific and consistency review, and refining the surviving proposals — without touching the file until the user explicitly approves.

Differs from /technical-paragraph-rewrite: that skill verifies a paragraph against the implementation and rewrites it. This skill starts from a reviewer comment and works backward to a revision that satisfies the comment while preserving manuscript quality.

Inputs Required

Provide:

  1. Comment(s): quoted verbatim (reviewer comment or finding from /section-review)
  2. Target: file and line range of the affected paragraph/section
  3. Context: preceding and following paragraph text (paste or cite file:line)
  4. Comment type (optional — helps skip irrelevant phases):
    • technical — challenges a factual claim about the implementation
    • writing — clarity, redundancy, flow, precision
    • consistency — terminology, notation, acronym
    • mixed — multiple types

Workflow

Phase 0 — Implementation Check (technical comments only)

Skip this phase for writing or consistency comments.

Invoke paper-implementation-checker with:

  • The affected paragraph (verbatim)
  • The implementation file most relevant to the challenged claim
What to verify Where to look
Type names, data structures, schemas <path>
Running examples <path>
Runtime behavior, interface method names <path>
Design intent / documentation <path>

Ask: "Does this paragraph accurately describe the implementation? Report CONSISTENT / DIVERGES / CANNOT_VERIFY with file:line evidence."

Read the full file on GitHub · 135 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 · 135 lines · 40 tokens per session scan A 22a6891d3603

Subscribe to this mod's changes

address-reviewer-comment is a skill published in the GitHub repository Rezenders/scientific_writing_agent (11 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 40 tokens to every session and 1,125 once invoked, about $0.0002 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.

Writing and docs
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