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 agentmods add skills/oprogramadorreal/optimus-claude/paper-initnpx skills add oprogramadorreal/optimus-claude --skill paper-initgit clone --depth 1 https://github.com/oprogramadorreal/optimus-claudeWrote 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/oprogramadorreal/optimus-claude/paper-init)<a href="https://agentmods.dev/skills/oprogramadorreal/optimus-claude/paper-init"><img src="https://agentmods.dev/badge/skills/oprogramadorreal/optimus-claude/paper-init.svg" alt="Measured on agentmods" 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.00102 | $0.04671 |
| Opus 5 | $0.00051 | $0.02336 |
| Sonnet 5 | $0.00020 | $0.00934 |
| Haiku 4.5 | $0.00010 | $0.00467 |
Grade A, and why
paper-init 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 345 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Paper Init
Build the local context bundle a later session needs to implement a research paper: the paper itself, its figures and references, what it specifies, what it leaves open, and its data. Context only — no implementation code, no stack setup. Everything the implementer needs must end up on disk; nothing may depend on this conversation's context.
The bundle
One paper/ directory at the project root holds everything paper-derived:
paper/README.md— bundle index: what this is, the read-first order, current status. Under ~50 lines.paper/source/— pristine originals only: the PDF (supplementary material included) plus the best machine-readable form available (EPUB, HTML, XML, arXiv LaTeX source), exactly as acquired. Derived files (text dumps, extracted markup) never live here.paper/source/metadata.json— the provenance record (step 2).paper/paper.md— the faithful working transcription (step 3).paper/tables.md— overflow tables, only when the transcription takes its escape hatch (step 3).paper/figures/+paper/figures/README.md— every figure, one README line each (file, dimensions, caption) with known defects — duplicates, missing diagrams — at the top.paper/references.md— every reference, annotated: role (dataset, baseline, method), resolved link, and fetch priority.paper/cited/— pristine sources of the works the paper, or a fetched work in turn, defers load-bearing content to (step 3), when any were fetched. Nothing derived lives here.paper/spec.md— what the paper actually specifies (step 3), ending with the targets the implementation is later judged against.paper/open-questions.md— what the paper leaves open (step 3).paper/dataset.md— dataset provenance and re-acquisition, when the paper uses datasets (step 6).paper/reference-code/— vendored existing code, when it exists (step 4); gitignored, its provenance tracked inmetadata.json.data/— the datasets themselves, gitignored, when any were acquired (step 6).
What ships with it
1 file 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.
- 2d ago Changed · +12 lines 689ddbf524cd
- 6d ago First seen · 333 lines · 102 tokens per session scan A 8a070b8c34d4
paper-init is a skill published in the GitHub repository oprogramadorreal/optimus-claude (73 stars, last pushed yesterday), licensed MIT. It adds 102 tokens to every session and 4,671 once invoked, about $0.0005 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
cran-extrachecks
Prepare R packages for CRAN submission by checking for common ad-hoc requirements not caught by devtools::check(). Use when: (1) Preparing a package for first CRAN release, (2) Preparing a package update for CRAN resubmission, (3) Reviewing a package to ensure CRAN compliance, (4) Responding to CRAN reviewer feedback.…
mirai
Help users write correct R code for async, parallel, and distributed computing using mirai. Use when users need to run R code asynchronously or in parallel, write mirai code with correct dependency passing, set up parallel workers, convert from future or parallel, use miraimap, integrate with Shiny or promises, or…
paper-opportunity-radar
Run a cumulative daily or retrospective sweep of research papers on a chosen topic, audit their claims, methods, integrity signals, and independent support, then identify overlooked but feasible project or business opportunities in a detailed source-grounded report. Use when asked to monitor papers every day, mine…
paper-verification
Use when the user wants to verify paper claims against code or data, audit numerical accuracy, check formula-code alignment, or validate citation accuracy. Triggers on phrases like "verify claims", "check numbers", "do the numbers match", "formula vs code", "audit the paper", or "cross-check results".
paper-writing
Use when the user wants to write, structure, or revise academic paper sections, improve notation consistency, or refine figures and tables. Triggers on phrases like "write the abstract", "structure the methods", "improve this section", "notation consistency", "figure refinement", or "paper structure".
using-cesiumjs-skills
Use when starting any conversation involving CesiumJS development - provides orientation on available domain skills and how they activate.