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 neqsim-pipeline-survey-processinggit 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/neqsim-pipeline-survey-processing)<a href="https://agentmods.dev/skills/equinor/neqsim-community-skills/neqsim-pipeline-survey-processing"><img src="https://agentmods.dev/badge/skills/equinor/neqsim-community-skills/neqsim-pipeline-survey-processing/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/neqsim-pipeline-survey-processing"><img src="https://agentmods.dev/badge/skills/equinor/neqsim-community-skills/neqsim-pipeline-survey-processing.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.00099 | $0.03397 |
| Opus 5.5 | $0.00040 | $0.01359 |
| Sonnet 5.5 | $0.00020 | $0.00679 |
| Haiku 4.5 | $0.00010 | $0.00340 |
Grade A, and why
neqsim-pipeline-survey-processing 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.
This is a copy
95% identical to neqsim-pipeline-survey-processing — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipeline Survey Processing
A pipeline hydraulic or integrity model needs an elevation profile. The profile almost always starts life as a survey file: thousands of rows of KP, depth to top of pipe, seabed depth and coordinates, produced by a different discipline, in a different datum, with null markers, duplicated stations, sections that belong to a neighbouring line, and a handful of points that are simply wrong.
The step from that file to a usable profile is where the numbers are decided, and it is normally done by hand in a spreadsheet with no record of what was done. This skill makes that step explicit and repeatable: every filter, sign flip, projection and rejection is written into a processing log that travels with the result, so a reviewer can see how the profile in front of them was produced.
It stops at the profile. Free spans and burial intervals are reported as geometric candidates for a qualified assessment - it does not perform modal, VIV, fatigue or stability analysis.
When to Use
- A survey or inspection export must become a pipeline elevation profile for a NeqSim pipe model.
- Erroneous points, null markers or duplicated stations need to be identified before a profile is trusted.
- Only part of a surveyed line is in scope, and the section between two structures must be extracted with the trim recorded.
- Free-span or cover candidates need to be located along KP as input to a DNV-RP-F105 or DNV-RP-F114 assessment.
- Two surveys of the same line, taken years apart, need a like-for-like change comparison.
- The survey lacks outer diameter and a value has to be supplied manually with the override recorded as a data gap.
When Not to Use
- As a free-span assessment. Span candidates here are geometry only; modal response, VIV screening and fatigue belong to DNV-RP-F105 and to a qualified pipeline engineer.
- As a positioning or datum authority. This skill normalises a sign convention and projects coordinates for screening; it does not perform geodetic datum transformation and must not be used to reconcile survey datums.
- To conclude that a pipeline has moved. A change between surveys can be datum, tide, or survey uncertainty as easily as real movement.
- On confidential survey files in a public workspace. Inputs must be public, synthetic, or approved for open-source use.
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.
- 1mo ago Changed · -57 tokens per session 49ce39df475a
- 1mo ago First seen · 267 lines · 156 tokens per session scan A 2b3d613c7bc2
neqsim-pipeline-survey-processing is a skill published in the GitHub repository equinor/neqsim-community-skills (4 stars, last pushed today), licensed Apache-2.0. It adds 99 tokens to every session and 3,397 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to neqsim-pipeline-survey-processing, differing in 0 lines, and is treated as a copy.
neqsim-pipeline-survey-processing compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| neqsim-pipeline-survey-processingequinor/neqsim-community-skills | Skill | 4 | today | Apache-2.0 | A | 99 | Claude Code, Codex |
| instrument-data-to-allotropeanthropics/knowledge-work-plugins | Skill | 35k | 3d ago | Apache-2.0 | A | 123 | Claude Code |
| exploratory-data-analysisK-Dense-AI/scientific-agent-skills | Skill | 56k | 4d ago | MIT | A | 83 | Claude Code |
| matlabK-Dense-AI/scientific-agent-skills | Skill | 56k | 4d ago | MIT | A | 44 | Claude Code |
| phylogeneticsK-Dense-AI/scientific-agent-skills | Skill | 56k | 4d ago | MIT | A | 71 | Claude Code, Codex |
| research-engineerdavila7/claude-code-templates | Skill | 33k | yesterday | MIT | A | 43 | Claude Code, Codex |
| mapping-to-snomedmaziyarpanahi/openmed | Skill | 5.8k | yesterday | Apache-2.0 | A | 205 | Claude Code |