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_exam_alignmentgit 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_exam_alignment)<a href="https://agentmods.dev/skills/equinor/neqsim/paperlab_exam_alignment"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/paperlab_exam_alignment/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_exam_alignment"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/paperlab_exam_alignment.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.00365 |
| Opus 5 | $0.00000 | $0.00182 |
| Sonnet 5 | $0.00000 | $0.00073 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
paperlab_exam_alignment 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 6d 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 Exam Alignment
Purpose
Check whether a PaperLab course book prepares students for the associated exercises and exams. Use this when a book has source folders with exams, exercise PDFs, review chapters, learning objectives, or end-of-chapter questions.
Inputs
source_manifest.jsonor a source root containingexams/andexercises/.- Chapter markdown files with learning objectives and exercise sections.
- Review/exam-preparation chapters.
- Optional extracted exam text from
paperlab-source-pdf-to-htmlor OCR.
Workflow
- Run
book-source-inventoryfor source traceability. - Run
python paperflow.py book-exam-alignment <book_dir>. - Review
exam_alignment.mdfor topics markedneeds-review. - For each weak topic, add a worked example, a self-test prompt, or a Chapter 26 review item.
- If exam PDF text is available, rerun with extracted text and update the topic matrix with evidence from actual problem statements.
Output
exam_alignment.jsonexam_alignment.md
Topic Matrix
At minimum, map:
- field-development framing,
- PVT and flow performance,
- processing and separation,
- subsea, wells, and SURF,
- economics and scheduling,
- optimization and uncertainty,
- regulation and standards,
- CCS and gas quality.
Safety Rules
- Do not reproduce confidential or copyrighted exam text unless allowed.
- Use topic frequencies and paraphrased problem types for public reports.
- Mark results as
needs-reviewwhen source PDFs have not been OCR/extracted. - Keep Chapter 26 concise; use cross-references to detailed worked examples in earlier chapters.
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.
- 6d ago First seen · 52 lines · 0 tokens per session scan A 078c8614cb0e
paperlab_exam_alignment is a skill published in the GitHub repository equinor/neqsim (151 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 365 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
self-improve-with-tinyfish
Enables Hermes to create new reusable skills for itself by researching live web sources with TinyFish Search and Fetch, analyzing source coverage, writing SKILL.md files, and installing them into Hermes memory. Use when the user asks Hermes to learn, teach itself, upgrade itself, or save a reusable capability.
Vibe Coding Mastery
The complete operating system for building software with AI. From first prompt to production deployment — prompting frameworks, architecture patterns, testing strategies, debugging playbooks, and production graduation checklists. Works with Claude Code, Cursor, Windsurf, Copilot, and any AI coding tool.
Image Processing Testing
Testing image processing pipelines including format conversion, resize quality, metadata handling, watermark verification, and thumbnail generation.
workshop-testing
Walk through the .NET AI Workshop as an attendee to validate that the READMEs, commands, and code snapshots still work. USE FOR: testing the workshop, testing a specific Part, dry-running the labs, verifying a README against its snapshot, reconciling or refreshing code snapshots, producing a workshop test report. DO…
Automation Interview Prep
Prepare for SDET and automation interviews round by round, covering coding screens, framework design, API testing tasks, scenario questions, and STAR stories built from real testing work.
ship-feature
End-to-end feature delivery — implement a feature, verify builds/tests pass, open a fully-filled draft PR, then automatically push every feedback round and review iteration to the same PR. Use when the user asks to implement or build a feature, fix-and-ship a change, or iterate on an existing feature PR.