neqsim-water-hammer

neqsim-water-hammer is a skill for Claude Code, Codex from equinor/neqsim. It costs 90 tokens per session (1,305 once invoked), scanned A, original, Apache-2.0.

A screening workflow for water hammer, the pressure surge caused by a rapid change in liquid flow, such as a valve closing or a pump stopping. It uses pipe routes, equipment data, and measured event records to estimate surge conditions.

In plain words
What is it for?
Use it to review fast valve closures, pump trips, check-valve slam, emergency shutdowns, and recorded pressure or flow events in liquid piping systems.
Why use it?
It helps identify lines at risk from sudden pressure changes before commissioning a detailed specialist surge study.

Skill for Claude CodeCodex

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

Good fit Use it to review fast valve closures, pump trips, check-valve slam, emergency shutdowns, and recorded pressure or flow events in liquid piping systems.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/equinor/neqsim/neqsim-water-hammer
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 --skill neqsim-water-hammer
Clone the repo
git clone --depth 1 https://github.com/equinor/neqsim

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-water-hammer

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/equinor/neqsim/neqsim-water-hammer"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/neqsim-water-hammer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 90 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,305 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00090 $0.01305
Opus 5.5 $0.00036 $0.00522
Sonnet 5.5 $0.00018 $0.00261
Haiku 4.5 $0.00009 $0.00130

Measured 1mo ago against content hash c32bdebda2c1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

neqsim-water-hammer 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 1mo 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.

.github/skills/neqsim-water-hammer/SKILL.md · 125 lines

How it starts

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

Water Hammer and Liquid Hammer Screening

Use this skill when a task involves hydraulic surge from fast valve movement, pump trip, check-valve slam, ESD closure, or other rapid liquid-flow changes. The core model is WaterHammerPipe; the workflow facade is WaterHammerStudy; MCP clients use runWaterHammer.

When To Use

  • Fast ESD or isolation-valve closure in water, condensate, oil, MEG, glycol, or other liquid-rich lines.
  • Pump trip, pump start, check-valve slam, or sudden flow setpoint changes.
  • STID/P&ID/E3D/stress-isometric route screening before a detailed surge study.
  • Tagreader event-window replay where measured pressure, flow, temperature, and valve position should override design-basis values.
  • Ranking which lines need detailed vendor or specialist surge analysis.

Do not use this as final pipe-stress approval. Treat it as a fast screening and evidence-pack workflow.

Workflow

  1. Extract line geometry from STID/P&ID/E3D/stress isometrics: length, internal diameter, wall thickness, roughness/piping class, elevation change, fittings, valves, and source references.
  2. Extract or infer event data: initiating valve, start time, closure/opening duration, start/end opening, pump trip status, and relevant controller action.
  3. Pull plant data with tagreader when available: inlet pressure, temperature, flow rate, valve opening, pump speed/status, and downstream pressure.
  4. Run WaterHammerStudy or MCP runWaterHammer with the equivalent route, field-data overrides, and event schedule.
  5. Report wave speed, Courant time step, wave round-trip time, Joukowsky surge, max/min pressure envelope, design-pressure margin, assumptions, and evidence.
  6. Recommend detailed surge analysis when peak pressure approaches design pressure, the route has varying diameters/branches, vapor cavities are likely, or support loads/stress checks are required.

MCP Input Pattern

{
  "studyName": "ESD valve closure screening",
  "model": "SRK",
  "temperature_C": 20.0,
  "pressure_bara": 45.0,
  "components": {"water": 1.0},
  "flowRate": {"value": 120000.0, "unit": "kg/hr"},
  "designPressure_bara": 95.0,
  "pipe": {
    "length_m": 1200.0,
    "diameter_m": 0.2032,
    "wallThickness_m": 0.0127,
    "roughness_m": 4.6e-5,
    "elevation_m": 8.0,
    "numberOfNodes": 80
  },
  "fieldData": {
    "inletPressure_bara": 46.0,
    "inletTemperature_C": 19.0,
    "flowRate_kg_hr": 118000.0,
    "valveOpening": 1.0
  },
  "eventSchedule": [
    {
      "type": "VALVE_CLOSURE",
      "startTime_s": 0.10,
      "duration_s": 0.15,
      "startOpening": 1.0,
      "endOpening": 0.0
    }
  ],
  "simulationTime_s": 4.0,
  "sourceReferences": [
    "generic STID line-list row",
    "generic tagreader event window"
  ]
}

Read the full file on GitHub · 125 lines

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. 1mo ago First seen · 125 lines · 90 tokens per session scan A c32bdebda2c1

Subscribe to this mod's changes

neqsim-water-hammer is a skill published in the GitHub repository equinor/neqsim (156 stars, last pushed today), licensed Apache-2.0. It adds 90 tokens to every session and 1,305 once invoked, about $0.0004 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-03.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens