neqsim-compressor-operating-window-check

neqsim-compressor-operating-window-check is a skill for Claude Code, Codex from equinor/neqsim-community-skills. It costs 52 tokens per session (1,129 once invoked), scanned A, original, Apache-2.0.

An educational check of whether a centrifugal compressor’s operating flow lies between its surge and stonewall limits. Surge is unstable low-flow operation; stonewall is the high-flow limit where performance can deteriorate.

In plain words
What is it for?
It is for quick compressor operating-window checks using operating flow and the two equipment limits.
Why use it?
It flags operating points that may be too close to either limit before detailed performance and anti-surge review.

Skill for Claude CodeCodex

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

Good fit It is for quick compressor operating-window checks using operating flow and the two equipment limits.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/equinor/neqsim-community-skills/compressor-operating-window-check
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 compressor-operating-window-check
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-compressor-operating-window-check

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/equinor/neqsim-community-skills/compressor-operating-window-check"><img src="https://agentmods.dev/badge/skills/equinor/neqsim-community-skills/compressor-operating-window-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,129 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.00052 $0.01129
Opus 5 $0.00026 $0.00564
Sonnet 5 $0.00010 $0.00226
Haiku 4.5 $0.00005 $0.00113

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

Security

Grade A, and why

neqsim-compressor-operating-window-check 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 12d ago.

The scan reads SKILL.md. This mod also ships 4 executable files (examples/basic_compressor_operating_window_check.py, src/compressor_operating_window/__init__.py, src/compressor_operating_window/model.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/compressor-operating-window-check/SKILL.md · 107 lines

How it starts

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

Compressor Operating Window Check

Use this skill for public, educational compressor operating window screening. It compares an operating flow against surge and stonewall limits to flag whether a centrifugal compressor operates inside a safe operating window before moving to validated performance and anti-surge review.

When to Use

  • When a user asks whether a compressor operating point is too close to surge or stonewall.
  • When an agent needs a quick operating-window triage to scope a compressor or debottlenecking study.
  • When examples must run without confidential performance maps, vendor curves, or anti-surge control settings.

Inputs

  • operating_flow: actual or required volumetric flow at the operating point in m3/h.
  • surge_flow: surge-limit flow at the same speed and conditions in m3/h.
  • stonewall_flow: stonewall or choke-limit flow at the same speed and conditions in m3/h.
  • min_surge_margin: minimum acceptable surge margin fraction, default 0.10.
  • min_stonewall_margin: minimum acceptable stonewall margin fraction, default 0.05.

Outputs

  • surge_margin_fraction: fractional distance from the operating point to the surge limit.
  • stonewall_margin_fraction: fractional distance from the operating point to the stonewall limit.
  • limiting_margin_fraction: the smaller of the two margins, where lower means closer to a limit.
  • operating_window_warning: ok, watch, or high.
  • assumptions: public assumptions used by the placeholder model.

Engineering Method

The Python class CompressorOperatingWindowModel uses open, published concepts only:

  • the surge margin is (operating_flow - surge_flow) / surge_flow.
  • the stonewall margin is (stonewall_flow - operating_flow) / stonewall_flow.
  • the limiting margin is the smaller of the two and drives rule-based warnings.
  • an operating point at or beyond either limit is flagged high; a margin below the minimum is flagged watch.

This is educational and screening-only logic. It is not a compressor performance standard, an anti-surge design method, a vendor method, or a replacement for validated performance review aligned with API 617 and a qualified process engineering review.

Read the full file on GitHub · 107 lines

Files

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.

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. 12d ago First seen · 107 lines · 52 tokens per session scan A 7517311da85a

Subscribe to this mod's changes

neqsim-compressor-operating-window-check is a skill published in the GitHub repository equinor/neqsim-community-skills (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 52 tokens to every session and 1,129 once invoked, about $0.0003 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

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…

anthropics/knowledge-work-plugins · 123 tokens

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.

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

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…

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

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.

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

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.

davila7/claude-code-templates · 43 tokens

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…

maziyarpanahi/openmed · 205 tokens