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 skills add Boom5426/Nature-Paper-Skills --skill paper-bootstrapgit clone --depth 1 https://github.com/Boom5426/Nature-Paper-SkillsWrote 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/boom5426/nature-paper-skills/paper-bootstrap)<a href="https://agentmods.dev/skills/boom5426/nature-paper-skills/paper-bootstrap"><img src="https://agentmods.dev/badge/skills/boom5426/nature-paper-skills/paper-bootstrap/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.
<a href="https://agentmods.dev/skills/boom5426/nature-paper-skills/paper-bootstrap"><img src="https://agentmods.dev/badge/skills/boom5426/nature-paper-skills/paper-bootstrap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 10 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Agent Snooping · line 20 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 21 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00039 | $0.01079 |
| Opus 5 | $0.00019 | $0.00540 |
| Sonnet 5 | $0.00008 | $0.00216 |
| Haiku 4.5 | $0.00004 | $0.00108 |
Grade A, and why
paper-bootstrap 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.
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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Paper Bootstrap
Overview
Use this skill to make a paper project writable before trying to make it good. The goal is not to generate boilerplate. The goal is to identify the real manuscript source of truth, create only the folders that help the workflow, and lock the project onto the correct venue and contribution framing early.
Default assumption: broad-impact journal work should start from the global Nature-style preference unless the user explicitly overrides the venue.
When the manuscript depends on experiments, figures, or results produced across multiple rounds, initialize lightweight project-state documents early so writing does not depend on memory alone: project_truth.md, decision_log.md, result_summary.md, and paper_handoff.md.
Use the helper script when you need a clean baseline layout quickly:
python ~/.codex/skills/paper-bootstrap/scripts/init_paper_layout.py path/to/paper
# Claude Code (global install): replace ~/.codex/skills with ~/.claude/skills
# Claude Code (project-local install): replace ~/.codex/skills with .claude/skills
When To Use
Use this skill when:
- A new paper directory is being created
- An existing paper directory has drafts, figures, notes, and outputs scattered across multiple places
- It is unclear which file is the active manuscript source of truth
- The project has no paper-specific memory yet
- The writing workflow needs a clean starting structure before revision begins
Do not use this skill for:
- Late-stage section polishing
- Figure-by-figure logic repair inside an already stable manuscript
- Conference-template conversion after the paper structure is already settled
Bootstrap Order
- Inspect the current paper directory before creating anything.
- Identify the active manuscript source of truth.
- Classify the paper's contribution type:
- method
- framework
- benchmark
- resource
- biological finding
- mixed, with one clearly dominant contribution
- Lock the working venue style:
- default to
Nature-style unless the user says otherwise - record venue-specific overrides only if they materially affect structure
- default to
- Create only the directories that the project actually needs.
- Create or reuse lightweight state files when they will reduce drift:
notes/project_truth.mdnotes/decision_log.mdnotes/result_summary.mdnotes/paper_handoff.md
- Save or update project memory with the stable local constraints.
- End with a short startup summary:
- active manuscript file
- dominant contribution type
- venue style
- missing assets or unresolved ambiguity
- recommended next revision step
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.
- 12d ago First seen · 116 lines · 39 tokens per session scan A 93777e811e5c
paper-bootstrap is a skill published in the GitHub repository Boom5426/Nature-Paper-Skills (490 stars, last pushed 6d ago), licensed MIT. It adds 39 tokens to every session and 1,079 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…