fit-page-limit

fit-page-limit is a skill for Claude Code, Codex from ShaishavMaisuria/research-paper-lifecycle-skills. It costs 202 tokens per session (1,266 once invoked), scanned A, original, Apache-2.0.

A paper-editing tool that plans how to reach a target page count. It identifies where a draft is too long and needs cuts, or too short and needs useful additional content.

In plain words
What is it for?
Use it to map the length of a LaTeX paper, prioritize sections to compress, decide where to add substance, and account for text, figures, tables, and venue rules.
Why use it?
It replaces guesswork about which sections are taking up space. This helps authors meet a conference or journal limit without cutting important ideas or adding filler.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to map the length of a LaTeX paper, prioritize sections to compress, decide where to add substance, and account for text, figures, tables, and venue rules.

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

Made for: Claude Code, Codex.

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 fit-page-limit

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/shaishavmaisuria/research-paper-lifecycle-skills/fit-page-limit"><img src="https://agentmods.dev/badge/skills/shaishavmaisuria/research-paper-lifecycle-skills/fit-page-limit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 202 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,266 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.00202 $0.01266
Opus 5 $0.00101 $0.00633
Sonnet 5 $0.00040 $0.00253
Haiku 4.5 $0.00020 $0.00127

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

Security

Grade A, and why

fit-page-limit 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 1 executable file (scripts/section_budget.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/fit-page-limit/SKILL.md · 123 lines

How it starts

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

Fit Page Limit

Two sides of the same problem: a paper that is over the limit and needs careful cuts, or a paper that is under and needs useful substance rather than filler. This skill maps the draft section by section, then gives the author a prioritized plan for whichever direction they need.

It coordinates with polish-prose for sentence-level tightening, refactor-structure for larger reorganization, polish-tables-figures for visual layout, and preflight-check when the page limit comes from a venue rule. Run it after the draft is roughly complete.

When to use

  • The draft is over the limit and the author needs to know where the bulk is.
  • The draft is under the target length and the author wants to use space well.
  • The author asks for a length map: "where is all my length going?"

Inputs

  • The .tex source.
  • The real compiled page count, if available, to calibrate the estimate.
  • The target: a venue page limit or a length the author names.
  • The venue CFP or profile, if the target comes from a venue.

Process

  1. Map the length. Run the analyzer from this skill directory; do not eyeball where the pages went.

    python3 scripts/section_budget.py paper.tex --target-pages 10 --current-pages 11
    

    It reports per-section words, percentage of the paper, estimated pages, and the over/under gap. --current-pages calibrates words per page to the author's actual compile. Use --json for machine-readable output.

  2. Confirm what counts. Re-verify the venue's limit and exclusions against the live CFP before relying on appendix moves or excluded sections. A stale page limit can desk-reject the paper.

  3. Pick the right branch. Use references/resize-tactics.md to turn the map into a value-aware resize plan.

If over: compress value-aware, never blind

Read the full file on GitHub · 123 lines

Files

What ships with it

2 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 · 123 lines · 202 tokens per session scan A 7b7738486008

Subscribe to this mod's changes

fit-page-limit 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 202 tokens to every session and 1,266 once invoked, about $0.0010 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