agentmods.dev

neqsim-tie-in-pipeline-concept

neqsim-tie-in-pipeline-concept is a skill for Claude Code, Codex from equinor/neqsim-community-skills. It costs 111 tokens per session (1,961 once invoked), scanned A, original, Apache-2.0.

A screening workflow for deciding whether a new oil or gas export pipeline can connect two facilities. It estimates possible landing points, seabed shape, pressure loss, cooling, wall thickness, and a nominal pipe size for each flow case.

In plain words
What is it for?
It is for early route and landing-point comparisons, hydraulic and thermal screening, pressure requirements, and preliminary wall-thickness and pipe-size recommendations.
Why use it?
It turns an early connection question into comparable engineering estimates and explains why one landing point or pipe size is preferred. It is not a detailed design for construction or for complex multiphase or hydrate cases.

Skill for Claude CodeCodex

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

not rated 4repo changed 7d ago A scan 111 tokens original Apache-2.0

Good fit It is for early route and landing-point comparisons, hydraulic and thermal screening, pressure requirements, and preliminary wall-thickness and pipe-size recommendations.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/equinor/neqsim-community-skills/neqsim-tie-in-pipeline-concept
View source ↗ equinor/neqsim-community-skills equinor.github.io
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 neqsim-tie-in-pipeline-concept
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-tie-in-pipeline-concept

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/equinor/neqsim-community-skills/neqsim-tie-in-pipeline-concept"><img src="https://agentmods.dev/badge/skills/equinor/neqsim-community-skills/neqsim-tie-in-pipeline-concept.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 111 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,961 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.00111 $0.01961
Opus 5.5 $0.00044 $0.00784
Sonnet 5.5 $0.00022 $0.00392
Haiku 4.5 $0.00011 $0.00196

Measured 7d ago against content hash 9173cd83a38f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

neqsim-tie-in-pipeline-concept 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 7d ago.

The scan reads SKILL.md. This mod also ships 6 executable files (src/tie_in_pipeline_concept/__init__.py, src/tie_in_pipeline_concept/candidates.py, src/tie_in_pipeline_concept/concept.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/subsea/neqsim-tie-in-pipeline-concept/SKILL.md · 137 lines

How it starts

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

Tie-in pipeline concept

Turns "can we connect A to B, with what pipe?" into numbers in minutes: candidate landing points, seabed profile, hydraulics, thermal decay and wall thickness. Built from the Martin Linge to Oseberg oil export screening (12 in x 9.5 mm X65, 44.5 km, 14 barg inlet at 2 600 Sm3/d, 26 barg at 6 000 Sm3/d).

When to Use

  • A host is being disconnected from its current export (tanker, FSO) or a new export route is wanted.
  • A study needs a profile figure, an inlet-pressure requirement and a size for a line of tens of km.
  • Several landing points are possible and the choice must be explained, not just picked.

Do not use for multiphase lines, gas export with hydrate or hydraulic stability issues, surge or pigging studies, or any design-grade basis.

Inputs

  • Source and landing facility: name, lat, lon (WGS84). Sodir facility coordinates are in the neqsim-ncs-infrastructure-network snapshot (hosts).
  • Oil properties (OilProperties): standard density, viscosity at inlet and sea temperature. Take them from the stabilised cargo or export stream of a NeqSim process model; flash at line conditions with water removed.
  • Rate cases in Sm3/d, a design case and a turndown case. Cite where each number comes from (measured production, forecast).
  • Design-basis overrides (basis_overrides): arrival pressure, design pressure, inlet temperature, steel grade, corrosion allowance, riser height. Every default is an assumption: list the ones you did not confirm.

Workflow

  1. rank_candidates(source, hosts, feeds_into, terminal_hosts, spare_capacity_fraction). Pass existing feeders from the network graph; the rationale string of every score term goes into the report.
  2. Choose the landing point with the user (or take rank 1 and say so).
  3. run_concept(...) or call build_profile, profile_statistics, size_pipeline separately. Cache EMODnet responses in references/emodnet/ of the task.
  4. Check: end-point depths against the reported facility water depth (a few metres), velocity window, inlet pressure against the design pressure, D/t limit, steep intervals in statistics['steep_intervals'].
  5. Cross-check the chosen size with NeqSim PipeBeggsAndBrills (segments of about 1 km, setElevation per segment, setConstantSurfaceTemperature plus setHeatTransferCoefficient). Keep the dry-oil fluid; do not pass water-containing cargo oil (a trace of water gave a second phase and a convergence failure in testing).
  6. Hand off to neqsim-tie-in-pid-sketch for the end connections and to an enterprise overlay skill for 3D views.

Read the full file on GitHub · 137 lines

Files

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.

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. 7d ago Changed · +2 lines 9173cd83a38f
  2. 15d ago Changed fba63bbf16c4
  3. 17d ago First seen · 135 lines · 111 tokens per session scan A 68d3df1ba315

Subscribe to this mod's changes

neqsim-tie-in-pipeline-concept is a skill published in the GitHub repository equinor/neqsim-community-skills (4 stars, last pushed today), licensed Apache-2.0. It adds 111 tokens to every session and 1,961 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-10-21.

PlanningScientific
Related

neqsim-tie-in-pipeline-concept compared with skills from other repositories

neqsim-tie-in-pipeline-concept next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
neqsim-tie-in-pipeline-conceptequinor/neqsim-community-skillsSkill4todayApache-2.0A111Claude Code, Codex
instrument-data-to-allotropeanthropics/knowledge-work-pluginsSkill35k3d agoApache-2.0A123Claude Code
exploratory-data-analysisK-Dense-AI/scientific-agent-skillsSkill56k4d agoMITA83Claude Code
matlabK-Dense-AI/scientific-agent-skillsSkill56k4d agoMITA44Claude Code
phylogeneticsK-Dense-AI/scientific-agent-skillsSkill56k4d agoMITA71Claude Code, Codex
research-engineerdavila7/claude-code-templatesSkill33kyesterdayMITA43Claude Code, Codex
mapping-to-snomedmaziyarpanahi/openmedSkill5.8kyesterdayApache-2.0A205Claude Code