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-release-source-termsgit 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-release-source-terms)<a href="https://agentmods.dev/skills/equinor/neqsim/neqsim-release-source-terms"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/neqsim-release-source-terms/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-release-source-terms"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/neqsim-release-source-terms.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.00083 | $0.02714 |
| Opus 5.5 | $0.00033 | $0.01086 |
| Sonnet 5.5 | $0.00017 | $0.00543 |
| Haiku 4.5 | $0.00008 | $0.00271 |
Grade A, and why
neqsim-release-source-terms 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 8d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Source Terms
When to use this
Use this skill to calculate an instantaneous release boundary condition or sample a release from a process inventory. First classify the opening as a short orifice, a finite-length pipe, or a depleting vessel/pipe inventory. Keep the selected model and its ReleaseModelEvidence with the result.
Use neqsim-consequence-analysis for downstream fire, dispersion, explosion, and fatality calculations. Use neqsim-depressurization-mdmt for vessel blowdown and MDMT. Use neqsim-trapped-liquid-fire-rupture for a pipe that heats and ruptures under fire. Those skills own their consequence workflows; this skill owns the source boundary only.
Class map
| Class | Package | What it does | Verified API |
|---|---|---|---|
ReleaseFlowModel, ReleaseFlowRequest, ReleaseFlowResult |
neqsim.process.safety.release |
Model-neutral instantaneous boundary and immutable status/evidence result | calculate(ReleaseFlowRequest), getStatus(), isUsable(), getMassFlowRateKgS() |
LegacyScreeningReleaseModel, LeakModel |
neqsim.process.safety.release |
Compatibility adapter for the historical leak-rate screening equation | getModelId(), getEvidence(); legacy model remains screening-level |
IdealGasReleaseModel |
neqsim.process.safety.release |
Calorically perfect, single-gas short-orifice equation | calculate(request) |
IdealGasFannoPipeReleaseModel, RealGasFannoPipeReleaseModel |
neqsim.process.safety.release |
Finite constant-area pipe release with Darcy friction; ideal-gas or EOS marching | calculate(request) |
HomogeneousEquilibriumReleaseModel |
neqsim.process.safety.release |
EOS-backed, isentropic short-opening flashing with equilibrium phase transfer and zero slip | calculate(request), getEvidence() |
DriftFluxHomogeneousEquilibriumReleaseModel, SlipCorrectedHomogeneousEquilibriumReleaseModel |
neqsim.process.safety.release |
Sensitivity alternatives that modify homogeneous phase velocity/area behavior | calculate(request), getMaximumGasAreaFraction() on drift-flux model |
FiniteRateDriftFluxReleaseModel, RanzMarshallFiniteRateReleaseModel, ComponentSelectiveFiniteRateReleaseModel |
neqsim.process.safety.release |
Finite-rate phase transfer using declared residence/relaxation inputs; optional component-specific times | Constructors accept surface tension and model-specific time/provenance inputs; calculate(request) |
PredictiveBubbleTransferZoneReleaseModel |
neqsim.process.safety.release |
Bounded vertical spherical-bubble transfer-zone screening with predicted bubble diameter, phase slip and residence time | Constructor accepts SI geometry, liquid properties, component diffusivities and provenance; calculate(request) |
RanzMarshallMassTransferCorrelation |
neqsim.process.safety.release |
Mass-transfer correlation used by finite-rate release models; not a standalone release-rate solver | getApplicabilityMessage(), getMorphology(), getSauterMeanDiameterM() |
ReleaseInventory |
neqsim.process.safety.release |
Coupled vessel inventory and opening whose mass changes during native process transient execution | run(UUID), getReleaseRequest(), getReleaseResult() |
IdealGasPipeDecompression, RealGasPipeDecompression |
neqsim.process.safety.release |
Coupled one-dimensional pipe-inventory decompression | run(UUID), getReleaseResult(), getReleaseProvenance() |
SourceTermSession, SourceTermFrame |
neqsim.process.safety.release |
Samples one or more process sources into sequenced, fingerprinted JSON/CSV frames | addSource(...), addLongPipeSource(...), capture(Map<String, UUID>), toJson(), toCsvRow() |
ReleaseModelEvidence, ReleaseSolidRiskAssessment |
neqsim.process.safety.release |
Explicit applicability/validation manifest and solid/hydrate risk guard | getEvidence(), getStatus() |
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.
- 8d ago Changed · +2 lines 38f88348e413
- 12d ago First seen · 126 lines · 83 tokens per session scan A 74adb2e47f65
neqsim-release-source-terms is a skill published in the GitHub repository equinor/neqsim (156 stars, last pushed today), licensed Apache-2.0. It adds 83 tokens to every session and 2,714 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-10-05.
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…