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-chapter-flow-editorgit 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-chapter-flow-editor)<a href="https://agentmods.dev/skills/equinor/neqsim/paperlab-chapter-flow-editor"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/paperlab-chapter-flow-editor/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-chapter-flow-editor"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/paperlab-chapter-flow-editor.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.00049 | $0.00684 |
| Opus 5.5 | $0.00020 | $0.00274 |
| Sonnet 5.5 | $0.00010 | $0.00137 |
| Haiku 4.5 | $0.00005 | $0.00068 |
Grade A, and why
paperlab-chapter-flow-editor 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_chapter_flow_editor — 2 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PaperLab Chapter Flow Editor
When to Use
USE WHEN: improving chapter structure, transitions, case continuity, or the overall reading path of a PaperLab book. This skill is useful after source coverage, figure generation, and notebook execution have already produced enough material, but before final typesetting.
DO NOT USE for: rewriting scientific claims without validation, changing numerical results, or deleting pedagogical repetition without review.
Chapter Arc
Each chapter should have a visible arc:
- Opening contract: what engineering decision or student capability the chapter supports.
- Concept foundation: the minimum theory, terminology, and physical logic.
- Engineering method: equations, workflow, or design procedure.
- Computational or case example: a worked use of the method.
- Decision consequence: what the result changes for concept selection, operation, risk, or economics.
- Transfer forward: how the output is reused in later chapters.
Flow Checks
Review the chapter for:
- abrupt section starts that need a one-sentence bridge,
- equations introduced before variables or intuition,
- figures placed before the concept needed to read them,
- repeated background that should become a cross-reference,
- case-study material that conflicts with the canonical case thread,
- summaries that repeat headings instead of synthesizing decisions,
- generated source or lecture-checkpoint texture in the main reading path.
Case Thread Pattern
When a recurring case is used across chapters, keep a small handoff pattern:
**Case handoff.** This chapter uses <input> from Chapter N, calculates <result>,
and carries <output> forward to Chapter M where it becomes <later use>.
Use this sparingly. One handoff per case-heavy chapter is usually enough.
Repetition Policy
Some repetition is useful for students; uncontrolled repetition is not. Keep:
- definitions that prevent a chapter from becoming inaccessible,
- summaries in review and exam-preparation chapters,
- short reminders before major calculations.
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 · 93 lines · 49 tokens per session scan A fe1e8323af63
paperlab-chapter-flow-editor is a skill published in the GitHub repository equinor/neqsim (156 stars, last pushed today), licensed Apache-2.0. It adds 49 tokens to every session and 684 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_chapter_flow_editor, differing in 2 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…