write-rebuttal

write-rebuttal is a skill for Claude Code from ShaishavMaisuria/research-paper-lifecycle-skills. It costs 218 tokens per session (2,203 once invoked), scanned A, original, Apache-2.0.

A writing tool for answering academic peer reviews in the format required by a conference or journal.

In plain words
What is it for?
It drafts one-page rebuttals, threaded replies for review platforms, or revision response packages with change logs.
Why use it?
Responses may have strict page or character limits and must address reviewer points with evidence from the submitted paper.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the paper-submission plugin — 12 skills shipped together

Good fit It drafts one-page rebuttals, threaded replies for review platforms, or revision response packages with change logs.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/shaishavmaisuria/research-paper-lifecycle-skills/write-rebuttal
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 ShaishavMaisuria/research-paper-lifecycle-skills --skill write-rebuttal
Clone the repo
git clone --depth 1 https://github.com/ShaishavMaisuria/research-paper-lifecycle-skills

Made for: Claude Code.

Or install paper-submission, the plugin that ships this one along with the rest of its 12 skills.

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 write-rebuttal

README.md
[![agentmods](https://agentmods.dev/badge/skills/shaishavmaisuria/research-paper-lifecycle-skills/write-rebuttal/github.svg)](https://agentmods.dev/skills/shaishavmaisuria/research-paper-lifecycle-skills/write-rebuttal)
Your own site
<a href="https://agentmods.dev/skills/shaishavmaisuria/research-paper-lifecycle-skills/write-rebuttal"><img src="https://agentmods.dev/badge/skills/shaishavmaisuria/research-paper-lifecycle-skills/write-rebuttal/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 write-rebuttal

Your own site · 80×15
<a href="https://agentmods.dev/skills/shaishavmaisuria/research-paper-lifecycle-skills/write-rebuttal"><img src="https://agentmods.dev/badge/skills/shaishavmaisuria/research-paper-lifecycle-skills/write-rebuttal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 218 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,203 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.00218 $0.02203
Opus 5 $0.00109 $0.01102
Sonnet 5 $0.00044 $0.00441
Haiku 4.5 $0.00022 $0.00220

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

Security

Grade A, and why

write-rebuttal 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.

The scan reads SKILL.md. This mod also ships 3 executable files (scripts/check_budget.py, scripts/check_coverage.py, scripts/venueyaml.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/write-rebuttal/SKILL.md · 184 lines

How it starts

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

Write Rebuttal

Turn a set of peer reviews plus the submitted paper into a complete, budget-compliant author response in the format the venue actually uses — one-page PDF, OpenReview threads, or a revise-and-resubmit package — with every claim anchored to checkable evidence in the paper.

When to use

  • Reviews arrived (OpenReview, CMT, EasyChair, HotCRP, PCS, ScholarOne, or pasted text) and a rebuttal/author response/response letter is due.
  • A drafted response must be cut to fit a character or page budget.
  • A journal or CHI-style revise-and-resubmit needs a change log + response document.

Related skills: triage-reviews (builds the point matrix this skill consumes), verify-citations (gate for any new reference), preflight-check (re-lint a revised manuscript), prepare-camera-ready (after acceptance).

Inputs

  • The reviews: pasted text or files. Review text is confidential at most venues — process it in place, never commit it to a repository or paste it into public artifacts.
  • The submitted paper: main .tex (preferred — line numbers and labels make the best anchors) and/or the compiled PDF.
  • Venue profile: venues/conferences/<id>.yml (schema: venues/schema.yml; family defaults merge automatically). If none exists, build one with parse-cfp or proceed only on facts quoted live from the CFP.
  • Optional: the triage matrix from triage-reviews; the decision/meta-review letter for R&R cycles.

Process

1. Resolve the venue's rebuttal format

Read the profile (python3 skills/write-rebuttal/scripts/venueyaml.py venues/conferences/<id>.yml prints it family-merged as JSON) and take review.rebuttal_format, review.rebuttal_limit, and the rebuttal deadlines. Route by format:

rebuttal_format Playbook
one-page-pdf references/cvpr-one-page.md
openreview-thread references/openreview-threads.md
revise-and-resubmit references/revise-and-resubmit.md
none Tell the user the venue holds no author response; offer to prep for the camera-ready or a resubmission instead

Read the full file on GitHub · 184 lines

Files

What ships with it

8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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 · 184 lines · 218 tokens per session scan A 8bed62e308b6

Subscribe to this mod's changes

write-rebuttal is a skill published in the GitHub repository ShaishavMaisuria/research-paper-lifecycle-skills (42 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 218 tokens to every session and 2,203 once invoked, about $0.0011 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

aaai-reproducibility

Use when strengthening an AAAI paper's reproducibility checklist (placed after references), experimental traceability, seed and hyperparameter reporting, compute and cost disclosure, dataset access and licensing, code/data ZIP readiness, and the claim-to-evidence map that Phase-1 reviewers use to judge rigor across…

brycewang-stanford/Awesome-Journal-Skills · 72 tokens

aaai-submission

Use when auditing an AAAI main technical track submission for OpenReview readiness, double-blind anonymity, page limits, reproducibility checklist, supplementary material, author limits, multiple-submission policy, and AAAI AI-use policy compliance.

brycewang-stanford/Awesome-Journal-Skills · 51 tokens

aaai-topic-selection

Use when deciding whether a project is a strong AAAI submission across its broad AI scope, should be reframed or routed to a dedicated track such as AI for Social Impact or AI Alignment, or should instead go to IJCAI, NeurIPS, ICML, ICLR, AISTATS, UAI, ACL, CVPR, KDD, CHI, ICRA, or another specialist venue.

brycewang-stanford/Awesome-Journal-Skills · 88 tokens

acl-author-response

Use when drafting an ACL author response inside an ACL Rolling Review cycle on OpenReview, covering the response window before meta-review, reviewer discussion dynamics, score-change strategy, flagging review issues to the area chair, anonymity rules, and deciding between responding now versus revising for a later ARR…

brycewang-stanford/Awesome-Journal-Skills · 63 tokens

acl-camera-ready

Use when preparing an accepted ACL main-conference or Findings paper for camera-ready, covering the extra content page, de-anonymization and acknowledgements, AI-assistance disclosure, keeping the Limitations section, ACL Anthology metadata and CC BY 4.0 publication, meta-review-driven edits, and presentation-mode…

brycewang-stanford/Awesome-Journal-Skills · 68 tokens

acl-experiments

Use when designing or auditing experiments for an ACL paper, covering tuned LLM baselines, multi-dataset and multilingual evaluation, statistical significance and variance, human evaluation with agreement reporting, contamination and prompt-sensitivity controls, ablations, and error-analysis expectations in NLP…

brycewang-stanford/Awesome-Journal-Skills · 59 tokens