paperlab-publication-calendar-scout

paperlab-publication-calendar-scout is a skill for Claude Code, Codex from equinor/neqsim. It costs 37 tokens per session (274 once invoked), scanned A, a copy of paperlab_publication_calendar_scout, Apache-2.0.

A skill for finding and tracking public calls for papers, special issues, conferences, and themed collections relevant to PaperLab and NeqSim research. It records deadlines, scope, sources, and topic matches.

In plain words
What is it for?
Use it to search publisher and venue pages, record submission information, match calls to current research, and identify preparation actions.
Why use it?
It keeps publication opportunities and their deadlines in one structured record instead of relying on scattered searches and notes.

Skill for Claude CodeCodex

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

Good fit Use it to search publisher and venue pages, record submission information, match calls to current research, and identify preparation actions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/equinor/neqsim/paperlab-publication-calendar-scout
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 equinor/neqsim --skill paperlab-publication-calendar-scout
Clone the repo
git clone --depth 1 https://github.com/equinor/neqsim

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 paperlab-publication-calendar-scout

README.md
[![agentmods](https://agentmods.dev/badge/skills/equinor/neqsim/paperlab-publication-calendar-scout/github.svg)](https://agentmods.dev/skills/equinor/neqsim/paperlab-publication-calendar-scout)
Your own site
<a href="https://agentmods.dev/skills/equinor/neqsim/paperlab-publication-calendar-scout"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/paperlab-publication-calendar-scout/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 paperlab-publication-calendar-scout

Your own site · 80×15
<a href="https://agentmods.dev/skills/equinor/neqsim/paperlab-publication-calendar-scout"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/paperlab-publication-calendar-scout.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 274 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.00037 $0.00274
Opus 5.5 $0.00015 $0.00110
Sonnet 5.5 $0.00007 $0.00055
Haiku 4.5 $0.00004 $0.00027

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

Security

Grade A, and why

paperlab-publication-calendar-scout 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 27d 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 paperlab_publication_calendar_scout — 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.

neqsim-paperlab/skills/paperlab-publication-calendar-scout/SKILL.md · 44 lines

What it actually says

PaperLab Publication Calendar Scout

When to Use

USE WHEN: aligning PaperLab papers and books with special issues, conferences, deadlines, or themed publication opportunities.

Calendar Fields

{
  "calls": [
    {
      "title": "Special issue on process systems engineering",
      "venue": "Journal name",
      "url": "https://example.org/call",
      "abstract_deadline": "2026-09-01",
      "submission_deadline": "2026-12-01",
      "matched_topics": ["optimization", "digital twin"],
      "readiness_action": "accelerate benchmark validation"
    }
  ]
}

Workflow

  1. Search public venue and publisher pages.
  2. Record deadlines, scope, article type, guest editors when public, and source URL.
  3. Match calls to active PaperLab opportunities and readiness levels.
  4. Recommend acceleration or retargeting actions.

Safety Rules

  • Do not use or store credentials for publisher sites.
  • Record the date each call was checked.
  • Do not infer acceptance likelihood from topical match.
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. 27d ago First seen · 44 lines · 37 tokens per session scan A a1ea4ea0b91a

Subscribe to this mod's changes

paperlab-publication-calendar-scout is a skill published in the GitHub repository equinor/neqsim (156 stars, last pushed today), licensed Apache-2.0. It adds 37 tokens to every session and 274 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to paperlab_publication_calendar_scout, differing in 2 lines, and is treated as a copy.

Related

Other skills, from other repositories

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens