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_health_dashboardgit 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_health_dashboard)<a href="https://agentmods.dev/skills/equinor/neqsim/paperlab_chapter_health_dashboard"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/paperlab_chapter_health_dashboard/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_health_dashboard"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/paperlab_chapter_health_dashboard.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.00043 | $0.00359 |
| Opus 5.5 | $0.00017 | $0.00144 |
| Sonnet 5.5 | $0.00009 | $0.00072 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
paperlab_chapter_health_dashboard 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-chapter-health-dashboard — 100% identical, 8 lines differ
What it actually says
PaperLab Chapter Health Dashboard
When to Use
USE WHEN: a book has multiple audit outputs and authors need a prioritized fix queue before release.
Pair with:
paperlab_book_typesetting_releasefor render gates,paperlab_scientific_traceability_auditfor evidence gates,paperlab_learning_objective_matrixfor teaching gates.
Score Dimensions
| Dimension | Inputs |
|---|---|
| structure | book-check, chapter front matter |
| evidence | evidence report, figure dossier |
| learning | objective matrix, exercise audit |
| technical | equation, API, standards audits |
| computation | notebook verification and regression status |
| figures | style and accessibility audit |
| prose | readability and conciseness audits |
Release Classes
ready: no blockers, only optional polish.minor-revision: small edits needed, no release blocker.major-revision: meaningful content or evidence gaps.blocked: render, evidence, API, notebook, or standards issue prevents release.
Output Pattern
| Chapter | Status | Confidence | Main Blocker | Next Fix |
|---------|--------|------------|--------------|----------|
| Ch10 | minor-revision | high | weak exercise coverage | Add one TEG sensitivity exercise |
Safety Rules
- Show missing audit data as confidence loss, not hidden failure.
- Do not average away blockers.
- Keep next fixes concrete and owned by a suitable agent.
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 First seen · 53 lines · 43 tokens per session scan A b848e2895e54
paperlab_chapter_health_dashboard is a skill published in the GitHub repository equinor/neqsim (156 stars, last pushed today), licensed Apache-2.0. It adds 43 tokens to every session and 359 once invoked, about $0.0002 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…