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-integrated-well-planninggit 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-integrated-well-planning)<a href="https://agentmods.dev/skills/equinor/neqsim-community-skills/neqsim-integrated-well-planning"><img src="https://agentmods.dev/badge/skills/equinor/neqsim-community-skills/neqsim-integrated-well-planning/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-integrated-well-planning"><img src="https://agentmods.dev/badge/skills/equinor/neqsim-community-skills/neqsim-integrated-well-planning.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.00117 | $0.06890 |
| Opus 5.5 | $0.00047 | $0.02756 |
| Sonnet 5.5 | $0.00023 | $0.01378 |
| Haiku 4.5 | $0.00012 | $0.00689 |
Grade A, and why
neqsim-integrated-well-planning 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integrated Well Planning
One repeatable workflow that turns reservoir information, fluid data, well requirements and facility constraints into a traceable well-design proposal, executable models, professional drawings and a well-planning report. It supports oil producers, gas and gas-condensate producers, water injectors and gas injectors, onshore, on platforms and subsea. The agent well-planning-engineer coordinates the study; this skill defines the schemas, methods, calculation tools, checks, drawing templates and report structure. The drilling and casing design module is the required skill neqsim-well-design-study.
The skill separates three things that must never be mixed up: implemented calculations (NeqSim classes with tests), screening estimates (executable but approximate or uncalibrated) and assessments not performed (they need an external tool or specialist; the skill then produces an interface specification, never a number). That separation is the capability ledger below and is printed in every report.
When to Use
- A well concept must be sized or compared: tubing size, wellhead/host back pressure, gas lift, completion arrangement, injection pressure and duty.
- A reservoir fluid and an IPR/injectivity basis exist and the question is deliverability, injectivity, temperatures, phase behaviour, hydrate margin and the operating envelope.
- A study needs a source/assumption register, a standards register, barrier schematics, A3 drawings, a decision/action log and a report that states what was and was not calculated.
- A hand-off to or from another agent is needed (VFP tables, trajectory, host constraints, PVT, cost/profile, flow-assurance requirements, integrity inputs).
- Do not use it for final design, rig-ready programmes, relief-well work, regulatory compliance statements or reservoir recovery/value estimates.
Inputs
The planning basis (iwp_planning_basis.v1, YAML or JSON, template: templates/planning_basis_template.yaml). Ranges are {low, base, high}; low is the pessimistic outcome, high the optimistic one (skin, water cut and host pressure are therefore taken from the opposite end of their range in the low case).
What ships with it
59 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.
- examples/gas_condensate_producer_subsea.yaml 6.9 KB
- examples/gas_injector_platform.yaml 6.3 KB
- examples/oil_producer_platform.yaml 6.6 KB
- examples/README.md 1.2 KB
- examples/run_cases.py 1.8 KB runs code
- examples/water_injector_onshore.yaml 6.3 KB
- pyproject.toml 1.0 KB
- README.md 1.8 KB
- schemas/iwp_cost_profile.v1.json 1.4 KB
- schemas/iwp_flow_assurance_requirements.v1.json 1.3 KB
- schemas/iwp_fluid_basis.v1.json 1.3 KB
- schemas/iwp_handoff_envelope.v1.json 1.1 KB
- schemas/iwp_host_constraints.v1.json 1.3 KB
- schemas/iwp_integrity_inputs.v1.json 1.2 KB
- schemas/iwp_interface_spec.v1.json 1.0 KB
- schemas/iwp_operating_envelope.v1.json 1.6 KB
- schemas/iwp_planning_basis.v1.json 3.8 KB
- schemas/iwp_trajectory.v1.json 1.5 KB
- schemas/iwp_vfp_request.v1.json 2.0 KB
- schemas/iwp_well_model.v1.json 1.2 KB
- src/integrated_well_planning/__init__.py 136 B runs code
- src/integrated_well_planning/__main__.py 48 B runs code
- src/integrated_well_planning/alternatives.py 11 KB runs code
- src/integrated_well_planning/barriers.py 12 KB runs code
- src/integrated_well_planning/basis.py 11 KB runs code
- src/integrated_well_planning/cli.py 4.8 KB runs code
- src/integrated_well_planning/datums.py 7.2 KB runs code
- src/integrated_well_planning/drawings_run.py 11 KB runs code
- src/integrated_well_planning/drilling_interfaces.py 8.0 KB runs code
- src/integrated_well_planning/envelope.py 10 KB runs code
- src/integrated_well_planning/examples_data.py 20 KB runs code
- src/integrated_well_planning/flow_assurance.py 10 KB runs code
- src/integrated_well_planning/handoff.py 16 KB runs code
- src/integrated_well_planning/hydraulics_compare.py 4.4 KB runs code
- src/integrated_well_planning/injectors.py 13 KB runs code
- src/integrated_well_planning/integrity.py 19 KB runs code
- src/integrated_well_planning/iwp_charts_extra.py 31 KB runs code
- src/integrated_well_planning/iwp_drawings.py 25 KB runs code
- src/integrated_well_planning/iwp_graphics.py 38 KB runs code
- src/integrated_well_planning/iwp_style.py 12 KB runs code
- src/integrated_well_planning/ledger.py 13 KB runs code
- src/integrated_well_planning/model_chain.py 16 KB runs code
- src/integrated_well_planning/nodal.py 5.3 KB runs code
- src/integrated_well_planning/planning_extras.py 4.7 KB runs code
- src/integrated_well_planning/producers.py 20 KB runs code
- src/integrated_well_planning/registers.py 10.0 KB runs code
- src/integrated_well_planning/report.py 20 KB runs code
- src/integrated_well_planning/runtime.py 9.1 KB runs code
- src/integrated_well_planning/standards.py 6.7 KB runs code
- src/integrated_well_planning/study.py 15 KB runs code
- templates/drawing_templates.md 1.2 KB
- templates/planning_basis_template.yaml 6.6 KB
- templates/report_outline.md 1.4 KB
- tests/conftest.py 1.1 KB runs code
- tests/test_basis_registers_datums.py 6.0 KB runs code
- tests/test_chain_java.py 12 KB runs code
- tests/test_envelope_standards_ledger_handoff.py 12 KB runs code
- tests/test_graphics.py 11 KB runs code
- tests/test_revb_extensions.py 14 KB runs code
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.
- 5d ago First seen · 215 lines · 117 tokens per session scan A ff704d3d2dff
neqsim-integrated-well-planning is a skill published in the GitHub repository equinor/neqsim-community-skills (4 stars, last pushed today), licensed Apache-2.0. It adds 117 tokens to every session and 6,890 once invoked, about $0.0005 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-11-01.
neqsim-integrated-well-planning compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| neqsim-integrated-well-planningequinor/neqsim-community-skills | Skill | 4 | today | Apache-2.0 | A | 117 | Claude Code, Codex |
| Analysis Summary ReportGGbond-bo/MemOmics-Agent | Skill | 31 | yesterday | MIT | A | 9 | Claude Code |
| lab_interpreterwananing/Smart-Health-Assistant | Skill | 39 | 1mo ago | MIT | A | 102 | Claude Code, Codex |
| spatial-visualizationShangBioLab/SpatialClaw | Skill | 11 | 5mo ago | Apache-2.0 | A | 48 | Claude Code, Codex |
| report-generatorhuifer/drug-discovery-skills | Skill | 22 | 10mo ago | none | A | 61 | Claude Code |
| 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 |