agentmods.dev

plan-submission

plan-submission is a skill for Claude Code from ShaishavMaisuria/research-paper-lifecycle-skills. It costs 155 tokens per session (1,681 once invoked), scanned A, original, Apache-2.0.

A deadline-planning tool for academic conference submissions. It works backward from a paper deadline and includes related milestones such as abstract registration, author-list freezes, review duties, supplementary files, and submission-system steps.

In plain words
What is it for?
Use it to plan a submission for a named conference and year, calculate time remaining with Anywhere on Earth deadlines, schedule account setup, and prepare for rebuttal or camera-ready stages.
Why use it?
Conference deadlines often involve earlier hidden deadlines and venue-specific rules. This turns them into dated tasks so authors can see what must happen and when.

Skill for Claude Code

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

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

not rated 55repo 3d ago A scan 155 tokens original Apache-2.0

Good fit Use it to plan a submission for a named conference and year, calculate time remaining with Anywhere on Earth deadlines, schedule account setup, and prepare for rebuttal or camera-ready stages.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/shaishavmaisuria/research-paper-lifecycle-skills/plan-submission
View source ↗ ShaishavMaisuria/research-paper-lifecycle-skills shaishavmaisuria.github.io
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 plan-submission
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 plan-submission

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/shaishavmaisuria/research-paper-lifecycle-skills/plan-submission"><img src="https://agentmods.dev/badge/skills/shaishavmaisuria/research-paper-lifecycle-skills/plan-submission.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 155 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,681 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.00155 $0.01681
Opus 5.5 $0.00062 $0.00672
Sonnet 5.5 $0.00031 $0.00336
Haiku 4.5 $0.00015 $0.00168

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

Security

Grade A, and why

plan-submission 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.

The scan reads SKILL.md. This mod also ships 3 executable files (scripts/build_timeline.py, scripts/fetch_page.py, scripts/venue_profile.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/plan-submission/SKILL.md · 136 lines

How it starts

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

Plan Submission

Turn "the deadline is in N weeks" into a dated, phase-aware milestone plan. Works backwards from the paper deadline (or forwards through rebuttal and camera-ready if the deadline already passed), anchored to a venues/conferences/<venue>-<year>.yml profile. Companion skills: parse-cfp (creates the profile), preflight-check (the T-3d desk-reject lint), write-rebuttal, prepare-camera-ready.

When to use

  • "Plan my SIGSPATIAL submission" / "what do I need to do before the deadline?"
  • "How many days until the NeurIPS deadline?" (AoE confusion included)
  • "When do I have to register the abstract?" / "when does the rebuttal start?"
  • The user just picked a venue (via select-venue) and asks "what now?"

Inputs

  • A venue + year (and ideally a track). The profile must exist at venues/conferences/<venue>-<year>.yml; if it does not, run parse-cfp first — never plan from remembered dates.
  • Today's date, and any user-specific constraints (vacations, co-author availability, experiments still running).
  • CONTACT_EMAIL env var if the live re-verification fetch is used.

Process

  1. Resolve the venue profile. Locate venues/conferences/<venue>-<year>.yml. Missing or from a previous cycle → route through parse-cfp to create/refresh it before planning. Check the profile's verified: block — if confidence is not verified-live or verified.date is old, treat every date as suspect.

  2. Re-verify the critical dates against the live CFP. Mandatory before the user relies on the plan. Run:

    python3 scripts/fetch_page.py "<cfp_url from the profile>"

    Confirm the abstract deadline, paper deadline, and timezone on the live page (deadlines slip mid-cycle — extensions are common, but so are silent corrections). On mismatch, update the profile first. If the page is JS-rendered or down, say so and mark the plan "dates unverified".

  3. Build the timeline. Run:

    python3 scripts/build_timeline.py venues/conferences/<venue>-<year>.yml \
    --track "<track>" --today YYYY-MM-DD

Read the full file on GitHub · 136 lines

Files

What ships with it

5 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 · 136 lines · 155 tokens per session scan A 682ffd423ec9

Subscribe to this mod's changes

plan-submission is a skill published in the GitHub repository ShaishavMaisuria/research-paper-lifecycle-skills (55 stars, last pushed 3d ago), licensed Apache-2.0. It adds 155 tokens to every session and 1,681 once invoked, about $0.0006 per session on Opus 5.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.

LaTeXPlanningResearchacademic-writingagent-skillsai-agentscitation-verificationliterature-review
Related

Other skills, from other repositories

research-manager

Use this when starting a new research project or managing a complex, multi-step research workflow.

poemswe/co-researcher · 21 tokens

academic-writing

You must use this when producing any research prose — literature reviews, syntheses, analyses, methodology descriptions, discussion sections, abstracts, or any written output intended for an academic audience.

poemswe/co-researcher · 39 tokens

systematic-review

You must use this when conducting PRISMA-standard systematic reviews, protocol development, or Risk of Bias assessment.

poemswe/co-researcher · 26 tokens

hypothesis-testing

You must use this when formulating testable hypotheses, designing experimental controls, or defining falsification criteria.

poemswe/co-researcher · 25 tokens

multi-source-investigation

You must use this when investigating complex claims across diverse sources or fact-checking contradictory information.

poemswe/co-researcher · 23 tokens

peer-review

You must use this when critiquing academic manuscripts, evaluating methodological rigor, or providing structured reviewer feedback.

poemswe/co-researcher · 24 tokens