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-trapped-liquid-fire-rupturegit 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-trapped-liquid-fire-rupture)<a href="https://agentmods.dev/skills/equinor/neqsim/neqsim-trapped-liquid-fire-rupture"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/neqsim-trapped-liquid-fire-rupture/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-trapped-liquid-fire-rupture"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/neqsim-trapped-liquid-fire-rupture.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.00109 | $0.05914 |
| Opus 5.5 | $0.00044 | $0.02366 |
| Sonnet 5.5 | $0.00022 | $0.01183 |
| Haiku 4.5 | $0.00011 | $0.00591 |
Grade A, and why
neqsim-trapped-liquid-fire-rupture 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 20d 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 — 520 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fire Rupture Study
This skill coordinates two related fire-rupture workflows:
- blocked-in liquid-filled segments exposed to fire, where thermal expansion can overpressure the pipe/flange system; and
- blowdown pipe segments exposed to fire, where a supplied pressure profile is combined with wall heat-up, temperature-dependent material data, and a Sellars-Tegart strain-rate model to estimate time to rupture.
For both workflows, gather evidence, preserve assumptions and gaps, run the appropriate NeqSim safety.rupture calculation, hand off any rupture source term, and produce a professional report output.
For source-document-driven blowdown pipe-fire studies, use the governed handoff
layer instead of calling the low-level solver directly: build
SafetyEvidenceReference entries, assemble a PipeFireRuptureDataSource, run
PipeFireRuptureStudyRunner, and report the returned
PipeFireRuptureStudyHandoff. This preserves calculation readiness, standards
readiness, deterministic uncertainty cases, and the post-rupture source-term
handoff in one JSON-safe package.
When the blowdown pressure profile has not yet been generated, first use the
dynamic flare/blowdown layer from neqsim-depressurization-mdmt: assemble
LineEquipmentListEvidence and DynamicBlowdownFlareStudyDataSource, run
DynamicBlowdownFlareStudyRunner, and use the returned source pressure profiles
and dynamic_blowdown_flare_load_handoff.v1 as the governed basis for the
pipe-fire rupture profile and flare/consequence handoff.
Use the workflow generically. Do not encode operator-specific criteria in public examples. If a private task has project-specific acceptance criteria, keep them inside the task folder and cite the private basis only in that task deliverable.
When to Use
- A Word report, technical note, or user request asks for a similar study on trapped liquid, blocked-in liquid, or no pressure relief on liquid-filled piping.
- A fire case can heat a liquid-filled segment isolated by closed valves or PBB.
- Thermal expansion may raise pressure above pipe, flange, gasket, or relief limits.
- The study needs PFP endurance, rupture time, source-term handoff, or an evidence matrix showing missing project data.
- A blowdown/depressurization pressure profile already exists and must be used to screen pipe wall heat-up, accumulated strain, rupture time, and release rate.
- P&ID, line-list, and piping-specification data must be assembled into pipe cases and reviewed by an engineer before calculation.
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.
- 20d ago Changed · -33 tokens per session 9c9e690a3c17
- 1mo ago First seen · 520 lines · 142 tokens per session scan A 3b8af632ced2
neqsim-trapped-liquid-fire-rupture is a skill published in the GitHub repository equinor/neqsim (156 stars, last pushed today), licensed Apache-2.0. It adds 109 tokens to every session and 5,914 once invoked, about $0.0004 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…