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 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/fem-coupling)<a href="https://agentmods.dev/skills/equinor/neqsim-community-skills/fem-coupling"><img src="https://agentmods.dev/badge/skills/equinor/neqsim-community-skills/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/fem-coupling"><img src="https://agentmods.dev/badge/skills/equinor/neqsim-community-skills/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.00369 | $0.09199 |
| Opus 5 | $0.00185 | $0.04600 |
| Sonnet 5 | $0.00074 | $0.01840 |
| Haiku 4.5 | $0.00037 | $0.00920 |
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 11d 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, STID 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.5 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.1 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.
- 11d ago First seen · 597 lines · 369 tokens per session scan A ca59829431df
neqsim-fem-coupling is a skill published in the GitHub repository equinor/neqsim-community-skills (2 stars, last pushed today), licensed Apache-2.0. It adds 369 tokens to every session and 9,199 once invoked, about $0.0018 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.
Other skills, from other repositories
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…