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 chtc66/academic-skills --skill review-rebuttalgit clone --depth 1 https://github.com/chtc66/academic-skillsWrote 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/chtc66/academic-skills/review-rebuttal)<a href="https://agentmods.dev/skills/chtc66/academic-skills/review-rebuttal"><img src="https://agentmods.dev/badge/skills/chtc66/academic-skills/review-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.
<a href="https://agentmods.dev/skills/chtc66/academic-skills/review-rebuttal"><img src="https://agentmods.dev/badge/skills/chtc66/academic-skills/review-rebuttal.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.00057 | $0.00532 |
| Opus 5 | $0.00028 | $0.00266 |
| Sonnet 5 | $0.00011 | $0.00106 |
| Haiku 4.5 | $0.00006 | $0.00053 |
Grade A, and why
review-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 13d 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.
What it actually says
Review Rebuttal
用这个 skill 处理投稿后的 reviewer comments、meta-review 和 rebuttal 草稿。重点是拆 concerns、区分补实验与澄清项、组织回复策略，并保持专业克制的语气。
工作流
- 逐个 reviewer 拆分意见，再汇总跨 reviewer 的共性 concern。
- 参考
references/review_taxonomy.md给 concern 分类。 - 参考
references/tone_guidelines.md约束语气和风险表达。 - 参考
references/rebuttal_template.md生成回复框架和草稿。
输入处理规则
- 接收 review 全文、meta-review、论文摘要、补充实验现状、作者说明。
- 如果用户只给摘要和 review，不要假装知道论文正文细节。
- 如果用户说“我们还没做这个实验”，在草稿中写成计划或澄清，不要写成已有结果。
- 支持多个 reviewer 合并分析，但要保留 reviewer 之间的差异。
输出规则
- 默认输出以下部分：
- 审稿意见拆分
- concern 分类
- 必须补实验的点
- 更适合澄清的点
- 回复策略
- rebuttal 草稿
- 高风险表述提醒
- 如果 reviewer 之间有冲突，单独指出，不要强行统一。
- 如果 meta-review 明确压住了某些意见，优先围绕 meta-review 组织总体策略。
证据与表述约束
- 不得编造实验、额外消融或人工分析结果。
- 不得假装已经补完实验。
- 不得使用对抗性或情绪化表述。
- 不要把 reviewer 的误解简单归咎于 reviewer 能力不足，应改写为“论文表述仍可更清楚地说明……”。
何时读引用文件
- 始终读取
references/rebuttal_template.md。 - 在 concern 分类时读取
references/review_taxonomy.md。 - 在起草回复时读取
references/tone_guidelines.md。
What ships with it
4 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.
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.
- 13d ago First seen · 49 lines · 57 tokens per session scan A 0b07924cdf53
review-rebuttal is a skill published in the GitHub repository chtc66/academic-skills (348 stars, last pushed 5mo ago), licensed MIT. It adds 57 tokens to every session and 532 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.
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…