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 neqsim-standard-requirement-extractiongit 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/neqsim-standard-requirement-extraction)<a href="https://agentmods.dev/skills/equinor/neqsim/neqsim-standard-requirement-extraction"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/neqsim-standard-requirement-extraction/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/neqsim-standard-requirement-extraction"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/neqsim-standard-requirement-extraction.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.00019 | $0.00547 |
| Opus 5.5 | $0.00008 | $0.00219 |
| Sonnet 5.5 | $0.00004 | $0.00109 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
neqsim-standard-requirement-extraction 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
92% identical to neqsim_standard_requirement_extraction — 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: NeqSim Standard Requirement Extraction
Purpose
Extract and map engineering requirements from standards or approved standards excerpts into a structured format that can support NeqSim book chapters, engineering reports, and design checks. Use this for NORSOK, DNV, API, ISO, IEC, ASME, and similar standards when clause-level traceability is needed.
Inputs
- A standards PDF or approved excerpt, when extraction is legally permitted.
- Existing chapter text or
standards_map.jsonto identify the target chapter and equipment context. - Optional OCR text for scanned standards.
Workflow
- Identify the standard code, revision, publisher, and license constraints.
- Extract only requirement-level statements using keywords such as
shall,should,may,required, and standard-specific forms. - Preserve section, clause, page, context-before, and context-after metadata.
- Classify each item as mandatory, recommendation, permission, information, or ambiguous.
- Link each item to chapters, equipment, or skills without copying large licensed text into public outputs.
- Use
book-standards-mapto summarize the chapter-level standard relevance.
Output Schema
{
"standard": "NORSOK D-010",
"revision": "latest-confirmed",
"source": "approved local excerpt",
"requirements": [
{
"id": "REQ-001",
"level": "mandatory",
"clause": "5.2",
"topic": "well barriers",
"text_excerpt": "short allowed excerpt or paraphrase",
"context": "why it matters for the chapter",
"mapped_chapters": ["ch14_drilling_and_wells"],
"status": "candidate"
}
]
}
Safety Rules
- Respect standards copyright and license restrictions.
- Prefer clause references and paraphrased summaries for public artifacts.
- Do not claim compliance from keyword extraction alone; human review is needed.
- Mark OCR-derived requirements as
needs-human-checkuntil reviewed.
Book Uses
- Chapter 7: separator and vessel design.
- Chapter 11: facility architecture, power systems, and design basis.
- Chapter 13: subsea and SURF systems.
- Chapter 14: wells and barriers.
- Chapter 21: NCS regulation and standards governance.
- Chapter 23: CO2 transport and injection integrity.
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 · 72 lines · 19 tokens per session scan A 55eae2161153
neqsim-standard-requirement-extraction is a skill published in the GitHub repository equinor/neqsim (156 stars, last pushed today), licensed Apache-2.0. It adds 19 tokens to every session and 547 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to neqsim_standard_requirement_extraction, 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…