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-standards-lookupgit 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-standards-lookup)<a href="https://agentmods.dev/skills/equinor/neqsim/neqsim-standards-lookup"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/neqsim-standards-lookup/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-standards-lookup"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/neqsim-standards-lookup.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.00082 | $0.07080 |
| Opus 5.5 | $0.00033 | $0.02832 |
| Sonnet 5.5 | $0.00016 | $0.01416 |
| Haiku 4.5 | $0.00008 | $0.00708 |
Grade A, and why
neqsim-standards-lookup 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 521 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NeqSim Standards Lookup
Reference for identifying, applying, and documenting industry standards compliance in every engineering task. All tasks — Quick, Standard, or Comprehensive — must identify applicable standards proportional to task depth.
Standards Identification (MANDATORY First Step)
Before any simulation or analysis, identify applicable standards:
| Task Scale | Standards Requirement |
|---|---|
| Quick | 1-line note: "Per [STANDARD]" or "N/A — property lookup" |
| Standard | Table of applicable standards with scope and status |
| Comprehensive | Full table with clause numbers, design values, and compliance evidence |
Search the Local Standards Library First (MANDATORY)
Before paraphrasing a standard from memory, citing it second-hand, or declaring it unobtainable, search the user's configured document root. It holds full PDFs and is more authoritative than recall:
neqsim --show-document-root # may be unset - then there is no library
neqsim documents "API 521" # recursive; every word must appear in the path
Words may be in any order and need not be adjacent ("API 521" finds
API STD 521 ...), but a standard filed under another body's number (for
example DNV-ST-F101) is only found by that exact designation. When several
editions are present (for example two TR3500 versions), cite the edition you
actually read.
Every task folder also carries the listing at
step1_scope_and_research/references/document_root_index.md — read it, since a
subagent may have no CLI access. Refresh it with neqsim documents --index ..
- Cite clause numbers from the PDF, not from memory. A remembered limit that turns out to be the previous edition is a silent compliance error.
- File names are indicative only. A document can contain the standard you need without naming it (company guidelines often embed API/NORSOK requirements), so open likely candidates before concluding it is absent.
- Copy the standards actually used into
references/literature/(ormanual/for company documents) so the task folder stays self-contained, and cite the document number instandards_applied. - Only after this search comes up empty may a standard be recorded as a
data_gap. When no document root is configured, say so explicitly in the gap entry rather than implying the standard does not exist.
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.
- 12d ago Changed · +6 lines 01630a79a992
- 1mo ago Changed · +27 lines a398ea745c7a
- 1mo ago First seen · 488 lines · 82 tokens per session scan A 18d65103e328
neqsim-standards-lookup is a skill published in the GitHub repository equinor/neqsim (156 stars, last pushed today), licensed Apache-2.0. It adds 82 tokens to every session and 7,080 once invoked, about $0.0003 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…