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.
npx skills add Haohaha-11/Paper-Writing --skill rebuttal-plannergit clone --depth 1 https://github.com/Haohaha-11/Paper-WritingWrote 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.
[](https://agentmods.dev/skills/haohaha-11/paper-writing/rebuttal-planner)<a href="https://agentmods.dev/skills/haohaha-11/paper-writing/rebuttal-planner"><img src="https://agentmods.dev/badge/skills/haohaha-11/paper-writing/rebuttal-planner/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.
<a href="https://agentmods.dev/skills/haohaha-11/paper-writing/rebuttal-planner"><img src="https://agentmods.dev/badge/skills/haohaha-11/paper-writing/rebuttal-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00770 |
| Opus 5 | $0.00000 | $0.00385 |
| Sonnet 5 | $0.00000 | $0.00154 |
| Haiku 4.5 | $0.00000 | $0.00077 |
Grade A, and why
rebuttal-planner 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.
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rebuttal Planner
Purpose
Turn reviews into a clear response strategy, concise rebuttal text, and a revision plan. The goal is not to "win an argument"; it is to reduce reviewer uncertainty with evidence, clarification, and concrete changes.
When To Use
- After receiving reviews.
- During author response or discussion periods.
- Before camera-ready revision planning.
- When deciding which new experiments or analyses are worth doing.
Inputs
Required:
- all reviewer comments with reviewer IDs;
- target venue response rules;
- paper context and contribution map;
- current evidence/results;
- constraints on rebuttal length.
Optional:
- draft response;
- new experiment results;
- paper-redteam report;
- claim-evidence matrix.
Procedure
-
Split comments into atomic issues. One reviewer paragraph may contain multiple issues.
-
Cluster issues. Use categories: novelty, correctness, experiments, baselines, clarity, citations, reproducibility, ethics, presentation, venue fit.
-
Assign decision impact. High impact issues affect soundness, novelty, or main evidence. Low impact issues are wording or presentation only.
-
Choose response type. Use: clarify, concede, correct misunderstanding, provide evidence, add experiment, add citation, revise text, or defer to limitations.
-
Draft response. Be concise, factual, respectful, and specific. Reference exact new evidence or planned revision.
-
Update revision plan. Every promised change must map to a paper section or artifact.
-
Mark residual risk. State what the response cannot fully solve.
Response Rubric
| Dimension | Strong | Weak |
|---|---|---|
| Specificity | Directly answers the issue | Generic thanks and restatement |
| Evidence | Points to result/text/change | Says "we believe" |
| Tone | Respectful and concise | Defensive or dismissive |
| Traceability | Maps to paper revision | No follow-up action |
| Honesty | Concedes real limitations | Overpromises |
Venue Adaptation
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.
- 12d ago First seen · 117 lines · 0 tokens per session scan A 09953add9912
rebuttal-planner 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 770 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…