paper-planning

paper-planning is a skill for Claude Code from CamusGIT/EvoQuant. It costs 166 tokens per session (2,054 once invoked), scanned A, a copy of paper-planning, Apache-2.0.

A four-step planning method for academic papers: shaping the story, planning experiments, designing figures, and scheduling the work.

In plain words
What is it for?
Use it to plan paper contributions, comparisons and ablation studies, method or teaser figures, and a four-week writing timeline.
Why use it?
It helps researchers decide what to claim and how to support those claims before they start writing. An ablation is an experiment that removes or changes one part of a method to test its effect.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it to plan paper contributions, comparisons and ablation studies, method or teaser figures, and a four-week writing timeline.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/camusgit/evoquant/paper-planning
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 CamusGIT/EvoQuant --skill paper-planning
Clone the repo
git clone --depth 1 https://github.com/CamusGIT/EvoQuant

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 paper-planning

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/camusgit/evoquant/paper-planning"><img src="https://agentmods.dev/badge/skills/camusgit/evoquant/paper-planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 166 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,054 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 100% copy Near-identical to another mod 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.00166 $0.02054
Opus 5.5 $0.00066 $0.00822
Sonnet 5.5 $0.00033 $0.00411
Haiku 4.5 $0.00017 $0.00205

Measured 1mo ago against content hash f6729c5c1b29, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

paper-planning 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 1mo 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.

Origin

This is a copy

100% identical to paper-planning — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

EvoQuant/skills/paper-planning/SKILL.md · 196 lines

How it starts

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

Paper Planning

A structured approach to planning academic papers before writing begins. Covers four key activities: Story design, Experiment planning, Figure design, and Timeline management.

When to Use This Skill

If you don't yet have an idea, use the research-ideation skill first to find a problem and design a solution.

  • User wants to plan a paper before writing
  • User asks about structuring a paper's story or contributions
  • User needs to plan experiments (comparisons, ablations)
  • User wants to design pipeline figures or teaser figures
  • User asks about writing timelines or submission schedules

Planning Overview

Paper planning follows four steps, ideally completed before writing begins:

Step 1: Story Design     → What is the narrative? What are the contributions?
Step 2: Experiment Plan   → What experiments prove our claims?
Step 3: Figure Design     → How do we visually communicate the method?
Step 4: Timeline          → When does each section get written?

Counterintuitive Planning First

Prioritize these counterintuitive rules before regular planning:

  1. Write your rejection letter first: Draft the top-5 likely rejection comments ("limited novelty", "missing baseline", "not robust", etc.), then plan experiments that directly preempt each one.
  2. Narrow claim before broad claim: Define the smallest defensible core claim first. Expand only after evidence is strong. Over-broad claims fail review more often than narrow strong claims.
  3. Design ablations before polishing method text: If a module cannot be ablated cleanly, its contribution claim is weak.
  4. Allocate compute to stress tests, not only benchmarks: A single convincing stress-test figure often contributes more than multiple small benchmark gains.
  5. Plan a fallback narrative now: If SOTA gain is marginal, predefine a secondary value proposition (efficiency, robustness, fewer assumptions, wider applicability).

See references/counterintuitive-planning.md

Read the full file on GitHub · 196 lines

Files

What ships with it

6 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. 1mo ago First seen · 196 lines · 166 tokens per session scan A f6729c5c1b29

Subscribe to this mod's changes

paper-planning is a skill published in the GitHub repository CamusGIT/EvoQuant (141 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 166 tokens to every session and 2,054 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to paper-planning, differing in 2 lines, and is treated as a copy.