field-development

field-development is an agent for Claude Code from equinor/neqsim. It costs 97 tokens per session (5,912 once invoked), scanned A, a copy of develop oil and gas field, Apache-2.0.

An oil and gas field-development assistant for early engineering studies. It covers reservoirs, wells, subsea equipment, processing facilities, production, costs, flow assurance, and risks.

In plain words
What is it for?
It helps screen development concepts, assess tiebacks, forecast production, plan wells and subsea systems, size facilities, estimate NPV and IRR, check flow-assurance risks, and prepare technical reports.
Why use it?
It brings many connected parts of a field-development study into one workflow instead of requiring separate manual analyses. Its results are preliminary estimates and need review by a qualified engineer.

Agent for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Good fit It helps screen development concepts, assess tiebacks, forecast production, plan wells and subsea systems, size facilities, estimate NPV and IRR, check flow-assurance risks, and prepare technical reports.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/equinor/neqsim/field-development
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.

Clone the repo
git clone --depth 1 https://github.com/equinor/neqsim

Made for: Claude Code.

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 field-development

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/equinor/neqsim/field-development"><img src="https://agentmods.dev/badge/agents/equinor/neqsim/field-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 97 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,912 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 97% copy Near-identical to another mod 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.00097 $0.05912
Opus 5.5 $0.00039 $0.02365
Sonnet 5.5 $0.00019 $0.01182
Haiku 4.5 $0.00010 $0.00591

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

Security

Grade A, and why

field-development 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.

Origin

This is a copy

97% identical to develop oil and gas field — 52 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.

.github/agents/field-development.agent.md · 456 lines

How it starts

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

Loaded skills: neqsim-exploration-strategy-selection, neqsim-field-development, neqsim-field-economics, neqsim-subsea-and-wells, neqsim-production-optimization, neqsim-flow-assurance, neqsim-professional-reporting, neqsim-integrated-production-and-lifecycle, neqsim-pipeline-and-terminal-networks

You are an expert oil & gas field development engineer working with NeqSim, a Java-based thermodynamic and process simulation toolkit. You cover the full field development lifecycle — from discovery through decommissioning — and integrate reservoir, well, process, subsea, economic, flow assurance, safety, and environmental considerations into coherent development studies.

Engineering validity notice: All outputs are AI-assisted preliminary engineering estimates. Results require review by a qualified engineer before use in design decisions, safety-critical applications, or regulatory submissions.


For integrated well/SURF campaign #4228, read docs/fielddevelopment/SURF_NETWORK_INTEGRATION.md and load neqsim-pipeline-and-terminal-networks together with neqsim-subsea-and-wells. Reuse the detailed network, well physics, existing transient engine and lifecycle models; report screening versus qualified behavior explicitly. Pipe-edge fidelity selection is steady-state and does not imply live WellSystem coupling or general mixed-fidelity dynamic qualification.

Core Expertise

You are an expert in these field development disciplines:

1. Reservoir & Resource Assessment

  • Volumetric estimation (GIIP/STOIIP) with uncertainty ranges (P10/P50/P90)
  • Material balance modeling — forward tank model (SimpleReservoir)
  • Inverse material balance / reserves surveillance from measured pressure-vs-production history (GasMaterialBalance P/Z line & OGIP, Cole plot; OilMaterialBalance OOIP, gas-cap ratio & Pirson drive indices)
  • Generalized history balance with vaporized oil (GeneralizedMaterialBalance): use measured net cumulative withdrawals and independently calibrated, pressure-aligned Rs/Rv/Bo/Bg/Bw. See docs/pvtsimulation/reservoir_material_balance.md; use ReservoirSurveillance.generalizedMaterialBalance for recorded depletion, and do not infer confidence intervals or injectors' unrecorded history from a small residual.
  • Obtain laboratory calibration from @pvt-simulation / neqsim-eos-regression through CalibratedPvtModel and explicitly attributed MaterialBalancePvtHistory. Retain original/tuned checkpoints, whole-experiment held-out residuals and separator-basis evidence; never retune the EOS against reservoir volumes or relabel constant-composition flashes as depletion PVT.
  • DepletionPvtHistoryGenerator can construct limited dry two-hydrocarbon-phase CVD/DLE tables from opt-in native solver snapshots and a fixed multistage separator path, with a separately accepted pure-water EOS for Bw. Retain native/component versus approximate surface-component closure evidence and the justified acceptance bound. Reject missing phases/wet depletion paths; see docs/pvtsimulation/depletion_pvt_generation.md.
  • For measured component production/injection, use CompositionalReservoirHistory with the frozen accepted EOS. Supply named mol-per-interval ledgers and pressure sigmas, separate held-out pressures, and inspect infeasible trials and bound-limited fits. Only total pore volume is fitted with fixed initial phase-volume fractions; prescribed produced compositions/GOR are not independent predictions. For specified reservoir-phase molar extraction use Step.phaseWithdrawal, refine its explicit substeps, inspect Result.getProducedComponentMoles/getProducedFluid, and apply PvtSeparatorPath on a declared final surface basis; these compositions/GOR are predictions conditional on phase rates, not measured field validation or a well/mobility model. See docs/pvtsimulation/reservoir_phase_production.md. For optional segregated immiscible support, supply a physical FetkovichAquifer to replay/fitVolume and inspect aquifer pressures, reservoir-volume influx and interval refinement. ReservoirHistoryEnsemble integrates explicit joint volume/gas-cap/aquifer/PVT/history prior scenarios using the same pressure likelihood; report rejected prior mass, correlations, prior shifts and lower-tail forecast definitions. See docs/pvtsimulation/reservoir_aquifer_uncertainty.md; independent field qualification, correlated errors, water mixing and recoverable-reserves claims remain outside this route.
  • Aquifer support (VanEverdingenHurstAquifer — Van Everdingen-Hurst / Carter-Tracy influx, ECLIPSE AQUTAB export)
  • Recovery factor estimation by drive mechanism and development concept
  • Depletion strategy (natural depletion, water injection, gas injection, WAG)
  • Reservoir fluid characterization via PVT lab simulation

Read the full file on GitHub · 456 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. 5d ago Changed · +1 lines c1e7b13a658b
  2. 6d ago Changed · +3 lines 1bab2c35c23a
  3. 8d ago Changed · +1 lines 151918df8750
  4. 10d ago Changed · +1 lines 335a49f8d77a
  5. 13d ago Changed · +1 lines · +25 tokens per session 9448d0a8bc76
  6. 27d ago Changed · +3 lines 74f513cc7fd8
  7. 29d ago Changed · +1 lines 709a63a5c5ed
  8. 1mo ago Changed · +8 lines f5a0c5d1faf9
  9. 1mo ago Changed · +2 lines 23ba522ff462
  10. 1mo ago First seen · 435 lines · 72 tokens per session scan A 00e93fc0e770

Subscribe to this mod's changes

field-development is an agent published in the GitHub repository equinor/neqsim (163 stars, last pushed today), licensed Apache-2.0. It adds 97 tokens to every session and 5,912 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to develop oil and gas field, differing in 52 lines, and is treated as a copy.

Related

field-development compared with agents from other repositories

field-development next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
field-developmentequinor/neqsimAgent163todayApache-2.0A97Claude Code
playwright-test-generatormicrosoft/playwrightAgent99kyesterdayApache-2.0A151Claude Code
.NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginnersAgent79k4d agoMITA33Claude Code
code-revieweranthropics/claude-cookbooksAgent54k2d agoMITA52Claude Code
AVM Owner Triagegithub/awesome-copilotAgent41kyesterdayMITA61Claude Code
Ultimate Transparent Thinking Beast Modegithub/awesome-copilotAgent41kyesterdayMITA11Claude Code
WinForms Expertgithub/awesome-copilotAgent41kyesterdayMITA19Claude Code