neqsim-cfd-coupling

neqsim-cfd-coupling is a skill for Claude Code, Codex from equinor/neqsim-community-skills. It costs 277 tokens per session (7,924 once invoked), scanned A, original, Apache-2.0.

An engineering workflow that connects NeqSim process simulation with CFD, or computational fluid dynamics, which calculates detailed flow around real equipment. It combines plant documents and data into a traceable design basis.

In plain words
What is it for?
It is for building or checking OpenFOAM studies, converting flashed fluid data into CFD boundary conditions, and feeding local flow results back into one-dimensional process models.
Why use it?
It replaces generic flow multipliers with results based on the actual geometry and fluid state, while keeping the design assumptions traceable.

Skill for Claude CodeCodex

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

Good fit It is for building or checking OpenFOAM studies, converting flashed fluid data into CFD boundary conditions, and feeding local flow results back into one-dimensional process models.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/equinor/neqsim-community-skills/cfd-coupling
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-community-skills --skill cfd-coupling
Clone the repo
git clone --depth 1 https://github.com/equinor/neqsim-community-skills

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-cfd-coupling

README.md
[![agentmods](https://agentmods.dev/badge/skills/equinor/neqsim-community-skills/cfd-coupling/github.svg)](https://agentmods.dev/skills/equinor/neqsim-community-skills/cfd-coupling)
Your own site
<a href="https://agentmods.dev/skills/equinor/neqsim-community-skills/cfd-coupling"><img src="https://agentmods.dev/badge/skills/equinor/neqsim-community-skills/cfd-coupling/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-cfd-coupling

Your own site · 80×15
<a href="https://agentmods.dev/skills/equinor/neqsim-community-skills/cfd-coupling"><img src="https://agentmods.dev/badge/skills/equinor/neqsim-community-skills/cfd-coupling.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 277 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 7,924 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.
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.00277 $0.07924
Opus 5 $0.00138 $0.03962
Sonnet 5 $0.00055 $0.01585
Haiku 4.5 $0.00028 $0.00792

Measured 10d ago against content hash 157faea38876, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

neqsim-cfd-coupling 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 10d ago.

The scan reads SKILL.md. This mod also ships 13 executable files (examples/multiphase_vof_case.py, examples/pid_to_openfoam_case.py, src/cfd_coupling/__init__.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/process/cfd-coupling/SKILL.md · 524 lines

How it starts

The opening of the file, as written. The whole thing — 524 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CFD Coupling

A one-dimensional model works in bulk quantities. Damage does not: it concentrates wherever the local flow field departs from the bulk — bends, welds, restrictions, headers, tube bundles. Screening models bridge that gap with generic textbook multipliers.

This skill closes the gap properly. It takes whatever is known about a component (P&ID, STID tag register, datasheets, plant data), takes the fluid from a NeqSim flash, builds and runs an OpenFOAM case on the real geometry, and converts the solved field back into the factor the one-dimensional model was guessing at. When a CFD study already exists it qualifies that study instead of running a new one.

Every layer works on its own. NeqSim and OpenFOAM are both optional: without NeqSim the fluid state is stated directly, and without OpenFOAM the case is still written and can be transferred and run elsewhere.

When to Use

  • A screening model needs a local enhancement factor and a generic multiplier is currently being assumed.
  • Pressure drop, velocity or wall shear is needed on real geometry rather than on an equivalent-length correlation.
  • Flow maldistribution across a bundle, manifold or header matters to the answer.
  • Two phases share the line and the interface matters - stratified, slug or annular flow, a free surface, or liquid accumulating in a low point.
  • A CFD report, vendor flow analysis or CFD/FEM deliverable is attached to an equipment tag and must be qualified before its numbers are used.
  • A new CFD run must be specified and needs fluid properties, turbulence inlet values and near-wall mesh sizing.
  • A tonal noise or vibration observation needs a fail-closed readiness decision before transient compressible CFD, acoustics, or structural coupling is scoped.

When Not to Use

  • As a substitute for a qualified CFD engineer on a design decision. This is a screening and coupling toolkit, not a verification-and-validation review.
  • To extract a number from a CFD study that fails the quality gate.
  • For droplet break-up statistics, separation efficiency or a dense dispersed phase. The multiphase screening will say lagrangian or euler_euler; those cases are recommended with a reason but not generated here.
  • For a temperature field. The generated cases solve momentum only, with the fluid properties frozen at the inlet flash. A stagnant or dead-leg region, a buoyancy-driven or thermally stratified region, or any wall-temperature question needs a buoyant conjugate solver (buoyantSimpleFoam, buoyantPimpleFoam, chtMultiRegionFoam) that this skill does not write. Use fem-coupling for the wall and near-wall temperature, and hand-build the buoyant case if the fluid-side field itself is the deliverable.
  • To diagnose a tonal aeroacoustic source with the generated steady RANS or incompressible VOF cases. Call assess_aeroacoustic_readiness first. A ready case still requires a separately configured transient compressible LES/DES, spectral pressure probes, acoustic propagation, and structural modal analysis when vibration is in scope.

Read the full file on GitHub · 524 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. 10d ago First seen · 524 lines · 277 tokens per session scan A 157faea38876

Subscribe to this mod's changes

neqsim-cfd-coupling is a skill published in the GitHub repository equinor/neqsim-community-skills (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 277 tokens to every session and 7,924 once invoked, about $0.0014 per session on Opus 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-08-31.

Related

Other skills, from other repositories

neuroskill-bci

Use live BCI cognitive and mood state from NeuroSkill.

NousResearch/hermes-agent · 18 tokens

ruview-advanced-sensing

Advanced RuView capabilities — RuvSense multistatic sensing (attention-weighted fusion, geometric diversity, persistent field model), cross-viewpoint fusion across multiple nodes, RF tomography (ISTA L1 solver, voxel grids), longitudinal biomechanics drift, pre-movement intention signals, adversarial signal detection…

ruvnet/RuView · 84 tokens

ruview-applications

Run RuView sensing applications — presence/occupancy, breathing & heart rate, activity & fall detection, 17-keypoint pose estimation (WiFlow), sleep monitoring & apnea screening, environment mapping, Mass Casualty Assessment (MAT), and the 3D point-cloud fusion demo. Use when someone wants to actually do something…

ruvnet/RuView · 79 tokens

lab-hardware-cad

Design custom laboratory hardware as parametric build123d models and export fabrication-ready STEP, STL, and DXF files - microfluidic chips and molds, optomechanical mounts and breadboard adapters, cuvette and microplate holders, tube racks, animal-behavior rigs, and 3D-printed instrument fixtures. Use when a research…

K-Dense-AI/scientific-agent-skills · 106 tokens

opentrons-integration

Author, review, migrate, simulate, and troubleshoot official Opentrons Python Protocol API v2 protocols for Flex and OT-2 robots. Use for robot-specific liquid handling, deck and labware setup, pipettes, modules, runtime parameters, liquid classes, and Opentrons App analysis. Use pylabrobot instead when one workflow…

K-Dense-AI/scientific-agent-skills · 79 tokens

pylabrobot

Develop and review PyLabRobot lab-automation resources, liquid-handling plans, offline simulations, and supported-device integrations. Use for PyLabRobot protocols or API questions; keep physical execution behind an explicit operator safety gate.

K-Dense-AI/scientific-agent-skills · 49 tokens