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 equinor/neqsim --skill paperlab_paper_to_book_chaptergit clone --depth 1 https://github.com/equinor/neqsimWrote 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/equinor/neqsim/paperlab_paper_to_book_chapter)<a href="https://agentmods.dev/skills/equinor/neqsim/paperlab_paper_to_book_chapter"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/paperlab_paper_to_book_chapter/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/equinor/neqsim/paperlab_paper_to_book_chapter"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/paperlab_paper_to_book_chapter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00033 | $0.00303 |
| Opus 5.5 | $0.00013 | $0.00121 |
| Sonnet 5.5 | $0.00007 | $0.00061 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
paperlab_paper_to_book_chapter 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.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- paperlab-paper-to-book-chapter — 94% identical, 2 lines differ
What it actually says
PaperLab Paper to Book Chapter
When to Use
USE WHEN: reusing a finished paper inside a textbook, monograph, course book, or professional handbook.
Transformation Pattern
| Paper element | Book adaptation |
|---|---|
| Abstract | chapter motivation and learning path |
| Methods | theory section plus implementation notes |
| Results | worked examples, figures, and exercises |
| Discussion | engineering interpretation and limitations |
| Supplementary data | notebooks and labs |
Workflow
- Extract validated claims, assumptions, figures, and citations.
- Add prerequisite context and learning objectives.
- Expand methods into stepwise explanations and worked examples.
- Turn sensitivity or benchmark results into exercises.
- Preserve provenance with a paper-to-chapter mapping.
Pass Criteria
- The chapter teaches rather than merely reprints the paper.
- Paper claims remain traceable to results or citations.
- Figures have observation, mechanism, implication, and recommendation discussion.
- Exercises support learning objectives.
Safety Rules
- Do not remove limitations or assumptions from paper results.
- Do not duplicate text in a way that creates self-plagiarism risk for submission contexts.
- Keep notebook outputs synchronized with chapter numbers and figure names.
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.
- 1mo ago Changed · +1 lines f2b440514b53
- 1mo ago First seen · 44 lines · 33 tokens per session scan A 4b123d165ed1
paperlab_paper_to_book_chapter is a skill published in the GitHub repository equinor/neqsim (156 stars, last pushed today), licensed Apache-2.0. It adds 33 tokens to every session and 303 once invoked, about $0.0001 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-09-03.
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.
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…
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…