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-release-orchestrationgit 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-release-orchestration)<a href="https://agentmods.dev/skills/equinor/neqsim/paperlab-book-release-orchestration"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/paperlab-book-release-orchestration/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-release-orchestration"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/paperlab-book-release-orchestration.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.00035 | $0.00412 |
| Opus 5.5 | $0.00014 | $0.00165 |
| Sonnet 5.5 | $0.00007 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
paperlab-book-release-orchestration 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
91% identical to paperlab_book_release_orchestration — 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.
What it actually says
PaperLab Book Release Orchestration
When to Use
USE WHEN: preparing a PaperLab book release candidate or regenerating all final artifacts after content, notebook, or figure changes.
Pair with:
paperlab-book-typesetting-releasefor output formats,paperlab-chapter-health-dashboardfor chapter readiness,paperlab-notebook-regression-baselinesfor computational gates.
Release Gate Order
- Source inventory and coverage check.
- Learning objective and curriculum checks.
- Scientific traceability, equation, API, and standards checks.
- Notebook verification and regression checks.
- Figure style and context checks.
- Conciseness and adversarial review.
- Chapter readiness dashboard.
- Render outputs and artifact freshness check.
- Final release gate report.
Blockers
Block release for:
- failed
book-check, - unresolved TODOs in release chapters,
- missing main figures,
- failed evidence check,
- broken NeqSim API examples,
- broken notebooks that support published claims,
- unsupported formal compliance language,
- render failures,
- stale standalone HTML or PDF after source edits.
Report Pattern
# Release Gate Report
- Book: <book slug>
- Date: <date>
- Decision: release | hold
- Commands run:
- <command>
- Blocking issues:
- <issue, owner agent, next action>
- Artifacts refreshed:
- `submission/book.html`
- `submission/book_standalone.html`
- `submission/book.pdf`
Safety Rules
- Do not publish when blocker audits fail.
- Record exact commands and environment details.
- Respect book-specific instructions for ignored source directories and render paths.
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 · 70 lines · 35 tokens per session scan A 71849812d2d1
paperlab-book-release-orchestration is a skill published in the GitHub repository equinor/neqsim (156 stars, last pushed today), licensed Apache-2.0. It adds 35 tokens to every session and 412 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to paperlab_book_release_orchestration, 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…