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-community-skills --skill neqsim-fem-couplinggit clone --depth 1 https://github.com/equinor/neqsim-community-skillsWrote 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-community-skills/neqsim-fem-coupling)<a href="https://agentmods.dev/skills/equinor/neqsim-community-skills/neqsim-fem-coupling"><img src="https://agentmods.dev/badge/skills/equinor/neqsim-community-skills/neqsim-fem-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.
<a href="https://agentmods.dev/skills/equinor/neqsim-community-skills/neqsim-fem-coupling"><img src="https://agentmods.dev/badge/skills/equinor/neqsim-community-skills/neqsim-fem-coupling.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.00126 | $0.08955 |
| Opus 5.5 | $0.00050 | $0.03582 |
| Sonnet 5.5 | $0.00025 | $0.01791 |
| Haiku 4.5 | $0.00013 | $0.00895 |
Grade A, and why
neqsim-fem-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 19d 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 — 597 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FEM Coupling
NeqSim solves the fluid. It reports a bulk temperature, a pressure and a set of transport properties, and a one-dimensional model turns those into a single U-value per pipe section. That works until the geometry stops being one-dimensional: a section of insulation floods, a clamp bridges the coating, a line is buried under a sloping seabed, a nozzle interrupts a shell. The heat then spreads in a direction the one-dimensional model does not have, and the U-value it was given is wrong by an amount nobody can estimate by hand.
This skill closes that gap. It takes whatever is known about the component (P&ID, tag register, datasheets, insulation specification, inspection report), takes the fluid side from a NeqSim flash, builds and solves the finite-element model of the solid, and converts the field back into the number the one-dimensional model needed - an effective U-value, a multiplier on it, a hot-spot factor, a no-touch time, a wall stress. When a thermal or stress finite-element study already exists, it qualifies that study instead of running a new one.
It is the solid-side companion to neqsim-cfd-coupling: same design-basis
discipline, same quality gate before any number is quoted, same handoff back into a
one-dimensional model. CFD resolves the fluid; FEM resolves the solid.
Every layer works on its own. NeqSim, Gmsh, scikit-fem and FEniCSx are all optional: without NeqSim the fluid state is stated directly, and without a mesher or a solver the geometry and the case are still written, with the commands needed to run them elsewhere.
When to Use
- A one-dimensional U-value is being assumed where the geometry is not one-dimensional: a local insulation defect or flooded section, a support or clamp, a buried line, a valve or flange with no insulation.
- A cooldown or no-touch time is needed and the wall's thermal inertia matters, not just the fluid's.
- A metal temperature is needed for a thermal-stress, MDMT or material-selection question, and the process-to-ambient difference is not the metal gradient.
- Species diffusion through a porous medium is being modelled and the molecular diffusivity has to come from the actual mixture.
- A thermal or thermo-mechanical finite-element report is attached to an equipment tag and its numbers are about to be used.
- A new finite-element run is being specified and needs film coefficients, a penetration depth, an element size and a time step.
What ships with it
22 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- examples/insulated_flowline_defect.py 13 KB runs code
- examples/subsea_cooldown.py 6.2 KB runs code
- pyproject.toml 962 B
- README.md 4.0 KB
- src/fem_coupling/__init__.py 4.6 KB runs code
- src/fem_coupling/conduction.py 31 KB runs code
- src/fem_coupling/design_basis.py 12 KB runs code
- src/fem_coupling/materials.py 11 KB runs code
- src/fem_coupling/mesh.py 25 KB runs code
- src/fem_coupling/model.py 17 KB runs code
- src/fem_coupling/solver.py 36 KB runs code
- src/fem_coupling/stress.py 12 KB runs code
- src/fem_coupling/thermal.py 19 KB runs code
- src/fem_coupling/visualise.py 14 KB runs code
- tests/test_conduction.py 8.4 KB runs code
- tests/test_fem_coupling_model.py 4.9 KB runs code
- tests/test_fem_design_basis.py 4.2 KB runs code
- tests/test_mesh.py 3.9 KB runs code
- tests/test_solver.py 8.1 KB runs code
- tests/test_stress.py 4.4 KB runs code
- tests/test_thermal.py 6.5 KB runs code
- tests/test_visualise_and_3d.py 4.2 KB runs code
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.
- 19d ago Changed c81c21ecbb47
- 1mo ago Changed · -107 tokens per session 8dfd3d5d0ba1
- 1mo ago First seen · 597 lines · 233 tokens per session scan A 19cf70acd828
neqsim-fem-coupling is a skill published in the GitHub repository equinor/neqsim-community-skills (4 stars, last pushed today), licensed Apache-2.0. It adds 126 tokens to every session and 8,955 once invoked, about $0.0005 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-19.
neqsim-fem-coupling compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| neqsim-fem-couplingequinor/neqsim-community-skills | Skill | 4 | today | Apache-2.0 | A | 126 | Claude Code, Codex |
| instrument-data-to-allotropeanthropics/knowledge-work-plugins | Skill | 35k | 3d ago | Apache-2.0 | A | 123 | Claude Code |
| exploratory-data-analysisK-Dense-AI/scientific-agent-skills | Skill | 56k | 4d ago | MIT | A | 83 | Claude Code |
| matlabK-Dense-AI/scientific-agent-skills | Skill | 56k | 4d ago | MIT | A | 44 | Claude Code |
| phylogeneticsK-Dense-AI/scientific-agent-skills | Skill | 56k | 4d ago | MIT | A | 71 | Claude Code, Codex |
| research-engineerdavila7/claude-code-templates | Skill | 33k | yesterday | MIT | A | 43 | Claude Code, Codex |
| mapping-to-snomedmaziyarpanahi/openmed | Skill | 5.8k | yesterday | Apache-2.0 | A | 205 | Claude Code |