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_source_pdf_to_htmlgit 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_source_pdf_to_html)<a href="https://agentmods.dev/skills/equinor/neqsim/paperlab_source_pdf_to_html"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/paperlab_source_pdf_to_html/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_source_pdf_to_html"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/paperlab_source_pdf_to_html.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.00000 | $0.00393 |
| Opus 5.5 | $0.00000 | $0.00157 |
| Sonnet 5.5 | $0.00000 | $0.00079 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
paperlab_source_pdf_to_html 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.
What it actually says
Skill: PaperLab Source PDF to HTML
Purpose
Convert or plan conversion of source PDFs into clean, searchable HTML for PaperLab books. Use this when lecture PDFs, public reports, exam PDFs, or standards excerpts need to be searchable by agents and linked to chapter figures, captions, and source manifests.
Inputs
- Book directory with
source_manifest.json, or a--source-rootfolder. - PDF files from lectures, exercises, exams, public reports, or approved reference documents.
- Optional OCR output for scanned/image-only PDFs.
Workflow
- Inventory source files with
book-source-inventory. - Run
python paperflow.py book-source-pdf-html-plan <book_dir>to create a conversion manifest. - Convert PDFs using the selected local converter. A robust converter should:
- preserve the source PDF,
- extract text and images,
- fall back to OCR or PyMuPDF when table-heavy PDFs fail,
- write HTML under an
_HTML/folder next to the source category.
- Feed converted HTML and extracted images into
technical_figure_understandingandfigure_dossier.json.
Output
source_pdf_html_plan.jsonsource_pdf_html_plan.md- Converted HTML files and extracted resources when the conversion script is run.
Quality Checks
- Count converted PDFs against the plan.
- Flag PDFs with very low extracted text length for OCR.
- Do not silently drop pages or figures.
- Record source path, output path, page count, text length, image count, and extraction method when the converter supports it.
Safety Rules
- Never delete or overwrite source PDFs.
- Do not publish converted HTML for non-public or licensed material unless that is explicitly allowed.
- For standards, extract only metadata or allowed excerpts unless the standard's license permits broader reproduction.
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 · 51 lines · 0 tokens per session scan A 73232810f4db
paperlab_source_pdf_to_html is a skill published in the GitHub repository equinor/neqsim (156 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 393 tokens. 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…