neqsim_standard_requirement_extraction

neqsim_standard_requirement_extraction is a skill for Claude Code, Codex from equinor/neqsim. It costs 17 tokens per session (546 once invoked), scanned A, original, Apache-2.0.

A workflow for extracting engineering requirements from approved standards such as ISO, API, DNV, or ASME. Standards are formal documents that define required or recommended practices.

In plain words
What is it for?
Use it to extract requirement text and metadata from standards, map items to chapters or equipment, and prepare structured engineering design checks.
Why use it?
It creates clause-level traceability and separates mandatory requirements from recommendations, permissions, and unclear statements.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to extract requirement text and metadata from standards, map items to chapters or equipment, and prepare structured engineering design checks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/equinor/neqsim/neqsim_standard_requirement_extraction
Install

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.

Any agent
npx skills add equinor/neqsim --skill neqsim_standard_requirement_extraction
Clone the repo
git clone --depth 1 https://github.com/equinor/neqsim

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for neqsim_standard_requirement_extraction

README.md
[![agentmods](https://agentmods.dev/badge/skills/equinor/neqsim/neqsim_standard_requirement_extraction/github.svg)](https://agentmods.dev/skills/equinor/neqsim/neqsim_standard_requirement_extraction)
Your own site
<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.

agentmods 80×15 button for neqsim_standard_requirement_extraction

Your own site · 80×15
<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>
Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 546 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00017 $0.00546
Opus 5.5 $0.00007 $0.00218
Sonnet 5.5 $0.00003 $0.00109
Haiku 4.5 $0.00002 $0.00055

Measured 1mo ago against content hash a24c8231f466, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.github/skills/neqsim_standard_requirement_extraction/SKILL.md · 72 lines

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.json to identify the target chapter and equipment context.
  • Optional OCR text for scanned standards.

Workflow

  1. Identify the standard code, revision, publisher, and license constraints.
  2. Extract only requirement-level statements using keywords such as shall, should, may, required, and standard-specific forms.
  3. Preserve section, clause, page, context-before, and context-after metadata.
  4. Classify each item as mandatory, recommendation, permission, information, or ambiguous.
  5. Link each item to chapters, equipment, or skills without copying large licensed text into public outputs.
  6. Use book-standards-map to 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-check until 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.

Read the full file on GitHub · 72 lines

Changes

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.

  1. 1mo ago Changed · +1 lines a24c8231f466
  2. 1mo ago First seen · 71 lines · 17 tokens per session scan A e67ccc2cbc68

Subscribe to this mod's changes

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 17 tokens to every session and 546 once invoked, about $0.0001 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.

Related

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens