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 reference-fluid-synthetic-generationgit 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/reference-fluid-synthetic-generation)<a href="https://agentmods.dev/skills/equinor/neqsim-community-skills/reference-fluid-synthetic-generation"><img src="https://agentmods.dev/badge/skills/equinor/neqsim-community-skills/reference-fluid-synthetic-generation/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/reference-fluid-synthetic-generation"><img src="https://agentmods.dev/badge/skills/equinor/neqsim-community-skills/reference-fluid-synthetic-generation.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.00227 | $0.02800 |
| Opus 5 | $0.00113 | $0.01400 |
| Sonnet 5 | $0.00045 | $0.00560 |
| Haiku 4.5 | $0.00023 | $0.00280 |
Grade A, and why
neqsim-reference-fluid-synthetic-generation 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 yesterday.
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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reference-Fluid Synthetic Generation
Use this skill for the "common reference fluid → adjust split factor → match measured data → generate representative fluids" workflow. It provides three plant-agnostic, dependency-free helpers:
match_split_factor— a robust golden-section 1-D search that finds the split / characterization factor best reproducing a measured target.generate_fluid_cases— build representative or synthetic fluid cases by applying a range of factors to a common reference fluid.blend_compositions— combine several well or fluid compositions into a single field composition by molar-rate allocation.
The forward model / fluid builder is injected by the caller, so this skill
has no dependency on a particular EOS. In practice it wraps the community
pseudocomponent-split-characterization gamma split or a NeqSim
characterization call, so the same factor drives both the split and the match.
When to Use
- When there is no PVT study at all — a discovery, a prospect, an early concept — and a reservoir model still needs a fluid. See No PVT data below.
- When you have a common reference EOS/fluid and want field-specific or per-case fluids by adjusting one heavy-end split factor (the "common factor" idea: reuse one characterization method with field-specific calibration).
- When a split factor must be calibrated so the model reproduces a measured saturation pressure, GOR, or stock-tank-oil density.
- When production is allocated across several wells or fluids and you need one representative field composition.
- When a complete PVT study is unavailable and you must generate a usable fluid from a reference plus available measurements.
No PVT data: build a best guess and say so
A reservoir model needs a fluid long before a laboratory PVT study exists, and often before a sample has been taken. The alternative to guessing silently is to guess explicitly.
from reference_fluid import build_analogue_fluid_basis
basis = build_analogue_fluid_basis(
depth_tvdss_m=3590.0,
province="northern_north_sea",
formation="Brent",
water_depth_m=381.0,
measured_temperature_C=129.0, # anything measured is used and labelled
measured_pressure_bara=542.0, # ... and anything absent is derived
)
basis.targets["gor_sm3_sm3"] # value + provenance + GOR DEFINITION
basis.seed["c7_plus_cuts"] # ready for addTBPfraction / addPlusFraction
basis.assumptions # each with the measurement that retires it
basis.acquisition_plan # ranked by how much it reduces the answer
What ships with it
8 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/reference_fluid_example.py 1.3 KB runs code
- pyproject.toml 671 B
- README.md 893 B
- src/reference_fluid/__init__.py 1.7 KB runs code
- src/reference_fluid/analogue_fluid.py 25 KB runs code
- src/reference_fluid/generate.py 6.4 KB runs code
- tests/test_analogue_fluid.py 11 KB runs code
- tests/test_generate.py 2.1 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.
- yesterday Changed · +95 lines · +120 tokens per session 5c19dcb53c89
- 11d ago First seen · 150 lines · 107 tokens per session scan A d55c5e70b0c0
neqsim-reference-fluid-synthetic-generation is a skill published in the GitHub repository equinor/neqsim-community-skills (2 stars, last pushed today), licensed Apache-2.0. It adds 227 tokens to every session and 2,800 once invoked, about $0.0011 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…