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-book-typesetting-releasegit 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-book-typesetting-release)<a href="https://agentmods.dev/skills/equinor/neqsim/paperlab-book-typesetting-release"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/paperlab-book-typesetting-release/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-book-typesetting-release"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/paperlab-book-typesetting-release.svg" alt="Reviewed on agentmods" width="80" 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.00055 | $0.00737 |
| Opus 5.5 | $0.00022 | $0.00295 |
| Sonnet 5.5 | $0.00011 | $0.00147 |
| Haiku 4.5 | $0.00006 | $0.00074 |
Grade A, and why
paperlab-book-typesetting-release 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.
This is a copy
100% identical to paperlab_book_typesetting_release — 4 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.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PaperLab Book Typesetting Release
When to Use
USE WHEN: preparing a PaperLab book for professional review, course release, or publisher submission. This skill checks rendered outputs, not only Markdown source. Use after content, figure, citation, and notebook checks are mostly stable.
DO NOT USE for: scientific validation of claims. Pair with
paperlab-scientific-traceability-audit for that.
Required Render Targets
For a release candidate, render at least:
python paperflow.py book-build books/<book> --format html --skip-notebooks --no-compile
python paperflow.py book-render books/<book> --format docx
python paperflow.py book-render books/<book> --format pdf
python paperflow.py book-render books/<book> --format odf
Use --format odf, not --format odt.
HTML Checks
- No horizontal page overflow at 500 px, 768 px, 1024 px, and desktop widths.
- Sidebar behavior is usable on desktop and hidden or collapsed on small screens.
- Cover, title, figures, equations, and tables are not clipped.
- Tables scroll horizontally only inside the table area, not the full page.
- KaTeX equations render without raw LaTeX showing in normal reading mode.
- Standalone HTML has embedded images when generated with the book-root
_embed_images.pyhelper.
PDF Checks
- Correct page size, margins, font size, and publisher profile.
- Chapter openings start cleanly, preferably recto for two-sided books.
- Running headers are absent from title pages and sensible on body pages.
- Tables use booktabs-style rules and do not overflow the text block.
- Figures stay close to their first reference and do not split from captions.
- Equations are numbered by chapter and do not collide with text.
- No orphan headings, widowed single lines, or large blank areas caused by floats.
DOCX Checks
- Equations become native Word equations when the OMML conversion dependency is available.
- Figure captions use consistent style and numbering.
- Cross-references and citation text survive conversion.
- Tables have readable column widths and no vertical-rule clutter.
- Heading levels map correctly to Word styles and table of contents generation.
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.
- 27d ago First seen · 90 lines · 55 tokens per session scan A 30508e4e5157
paperlab-book-typesetting-release is a skill published in the GitHub repository equinor/neqsim (156 stars, last pushed today), licensed Apache-2.0. It adds 55 tokens to every session and 737 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to paperlab_book_typesetting_release, differing in 4 lines, and is treated as a copy.
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…