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 water-dewpoint-dehydration-screeninggit 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/water-dewpoint-dehydration-screening)<a href="https://agentmods.dev/skills/equinor/neqsim-community-skills/water-dewpoint-dehydration-screening"><img src="https://agentmods.dev/badge/skills/equinor/neqsim-community-skills/water-dewpoint-dehydration-screening/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/water-dewpoint-dehydration-screening"><img src="https://agentmods.dev/badge/skills/equinor/neqsim-community-skills/water-dewpoint-dehydration-screening.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.00101 | $0.02140 |
| Opus 5 | $0.00051 | $0.01070 |
| Sonnet 5 | $0.00020 | $0.00428 |
| Haiku 4.5 | $0.00010 | $0.00214 |
Grade A, and why
neqsim-water-dewpoint-dehydration-screening 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 today.
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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Water Dewpoint Dehydration Screening
Use this skill for public, educational gas water-content screening. It estimates the saturated water content of natural gas using the open GPSA Bukacek correlation and compares it to a sales-gas water specification so an agent can flag whether dehydration is likely required before detailed design.
When to Use
- When a user asks whether a gas stream needs dehydration to meet a water spec.
- When an agent needs a quick saturated-water-content estimate to scope a dehydration study.
- When examples must run without confidential dehydration designs, glycol data, or company gas specs.
- Before asserting any hydrate, ice, or free-water finding — run the saturation test below to establish whether free water is actually available. A hydrate finding built on an unverified water number is the single easiest way to produce a confident wrong answer.
Is the stream already dehydrated? — the saturation test
A stated water content in a datasheet or stream table tells you nothing on its own; you have to compare it against saturation at the same pressure and temperature.
ratio = stated_water_content / saturated_water_content(P, T)
ratio ~ 1.0 -> stream is AT SATURATION: wet gas, free water available.
Water was removed (if at all) by COOLING + KNOCK-OUT, not dehydration.
ratio << 1 -> stream is DEHYDRATED (glycol contactor or molecular sieve upstream).
Typical TEG: 30-50 ppm(mol); typical sales-gas spec: ~100 ppm(mol).
ratio > 1.0 -> the stated composition carries entrained/free water, or the stated
P/T is not the condition the composition belongs to. Resolve before use.
Dewatering is not dehydration
This is the trap the test exists to catch. A suction scrubber, knock-out drum, or cooler + separator removes free water and leaves the gas exactly at saturation at the separator outlet condition. It lowers the absolute water content but gives zero dryness margin — the stream re-condenses water on any subsequent cooling or expansion. Only a glycol contactor or a molecular sieve produces an actual water dew-point depression.
What ships with it
6 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.
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.
- today Changed · +61 lines · +35 tokens per session 0699a9960b9d
- 12d ago First seen · 101 lines · 66 tokens per session scan A b0411c2fe90b
neqsim-water-dewpoint-dehydration-screening is a skill published in the GitHub repository equinor/neqsim-community-skills (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 101 tokens to every session and 2,140 once invoked, about $0.0005 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…
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.
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…
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…