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 book-creationgit 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/book-creation)<a href="https://agentmods.dev/skills/equinor/neqsim/book-creation"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/book-creation/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/book-creation"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/book-creation.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.00018 | $0.06822 |
| Opus 5.5 | $0.00007 | $0.02729 |
| Sonnet 5.5 | $0.00004 | $0.01364 |
| Haiku 4.5 | $0.00002 | $0.00682 |
Grade A, and why
book-creation scanned grade A with 1 finding 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
subprocess.check_call([sys.executable, "-m", "pip", "install", "-q", "neqsim"]) This is a copy
97% identical to book_creation — 8 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 — 734 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Book Creation in PaperLab
When to Use
USE WHEN: creating a new scientific book project, writing chapter content,
running book notebooks, building/rendering a book, or troubleshooting the book
pipeline. This skill covers the complete lifecycle from book-new to final
rendered outputs in HTML/Word/PDF/ODF.
DO NOT USE for: paper writing workflows (use write-methods-section,
journal-formatting, etc. instead).
1. Book Project Structure
Every book lives under neqsim-paperlab/books/<slug>_<year>/. The critical
file is book.yaml — it defines metadata, chapter ordering, parts, and
rendering settings.
books/<book_slug>/
├── book.yaml # Master manifest — defines EVERYTHING
├── refs.bib # Master bibliography
├── nomenclature.yaml # Symbol definitions
├── frontmatter/
│ ├── title_page.md
│ ├── copyright.md
│ ├── dedication.md
│ └── preface.md
├── chapters/
│ ├── ch01_introduction/
│ │ ├── chapter.md # Chapter text (markdown with LaTeX math)
│ │ ├── figures/ # Generated figures (PNG)
│ │ └── notebooks/ # Jupyter notebooks that generate figures
│ ├── ch02_topic_name/
│ │ ├── chapter.md
│ │ ├── figures/
│ │ └── notebooks/
│ └── ...
├── backmatter/
│ ├── glossary.md
│ └── author_bio.md
└── submission/ # Rendered outputs
├── book.html
├── book.docx
├── book.pdf
├── book.odt
└── figures_chNN/ # PDF renderer copies figures here for Typst
book.yaml Structure
title: "Book Title"
subtitle: "Subtitle"
authors:
- name: "Author Name"
affiliation: "Institution"
email: "[email protected]"
edition: "1st"
year: 2026
publisher: "springer" # springer | wiley | crc | self
language: "en"
settings:
book_type: "textbook" # simple | technical | textbook (see §1.1)
page_size: "b5" # b5 | a4
font_size: 10
line_spacing: 1.2
two_sided: true
chapter_numbering: true
equation_numbering: "chapter" # chapter-scoped: Eq. 3.1, 3.2, ...
# Optional content toggles (override the book_type profile, see §1.1):
# include_copyright: true
# include_learning_objectives: true
# include_exercises: true
# exclude_sections: ["Review Questions", "Problems"]
frontmatter:
- title_page
- copyright
- dedication
- preface
parts:
- title: "Part I: Foundations"
chapters:
- dir: "ch01_introduction" # MUST match exact dir name
title: "Introduction and Context"
- dir: "ch02_topic_name"
title: "Topic Name"
- title: "Part II: Advanced"
chapters:
- dir: "ch03_another_topic"
title: "Another Topic"
backmatter:
- glossary
- author_bio
nomenclature:
file: "nomenclature.yaml"
position: "after_toc"
bibliography:
style: "numeric"
file: "refs.bib"
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 · 734 lines · 18 tokens per session scan A fd3d181855de
book-creation is a skill published in the GitHub repository equinor/neqsim (156 stars, last pushed today), licensed Apache-2.0. It adds 18 tokens to every session and 6,822 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). It is 97% identical to book_creation, differing in 8 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…