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-reservoir-history-match-forecastgit 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-reservoir-history-match-forecast)<a href="https://agentmods.dev/skills/equinor/neqsim-community-skills/neqsim-reservoir-history-match-forecast"><img src="https://agentmods.dev/badge/skills/equinor/neqsim-community-skills/neqsim-reservoir-history-match-forecast/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-reservoir-history-match-forecast"><img src="https://agentmods.dev/badge/skills/equinor/neqsim-community-skills/neqsim-reservoir-history-match-forecast.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.00095 | $0.02424 |
| Opus 5.5 | $0.00038 | $0.00970 |
| Sonnet 5.5 | $0.00019 | $0.00485 |
| Haiku 4.5 | $0.00010 | $0.00242 |
Grade A, and why
neqsim-reservoir-history-match-forecast 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 27d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reservoir History Match and Forecast
A reservoir model cheap enough to re-match whenever new data arrives, with a compositional fluid, that feeds the process model with the fluid the wells actually produce.
When to Use
- A gas or gas-condensate field with several formations, compartments or wells must be matched to its production history and forecast.
- The produced composition changes with depletion and the process model should see it.
- Production and composition must be shown for history and future through a process model.
- Not for black-oil or volatile-oil reservoirs with mobile oil (use the grid route in
neqsim-near-well-and-injectivity) and not for open-data volume screening (neqsim-reservoir-model-builder).
Inputs
- Daily well gas, condensate, water, on-stream hours, wellhead pressure, downhole pressure.
- Field allocated gas, condensate and water series.
- Well-to-formation and compartment map; initial pressure and temperature per tank.
- Tuned reservoir fluid per formation (NeqSim EOS, component names, heavy indices).
- Scenario: target rate, minimum wellhead pressure, well schedule.
Outputs
- Matched tank parameters (
giip_gsm3,aquifer_c,cgr_scale,heavy_scale) with std and bound hits. - Match quality by observation kind and tank.
- Well deliverability (a, c) and water-gas ratio.
- Produced composition and condensate-gas ratio versus date and pressure.
- History and forecast tables per tank and well; P10/P50/P90 when identifiable.
- Wellstream tables (composition, molar rate, water, WHP) for process models and process KPI series.
Engineering Method
Model. A tank is one reservoir, formation or pressure compartment with its own fluid, volume
(giip_gsm3, wet gas in place as standard gas volume), optional Schilthuis aquifer (aquifer_c) and a
condensate-yield scale (cgr_scale). The depletion path (DepletionPath) is a constant-volume
depletion on a NeqSim EOS: moles left, liquid saturation, produced-stream composition and surface
yield versus pressure. It depends on pressure only, so it is computed once per fluid and the material
balance looks pressure up from cumulative moles produced. A well has deliverability
P_res^2 - WHP^2 = a q + c q^2 fitted from daily history and a share of each tank it drains. A field
is tanks + wells + optional tank connections. History is driven by well gas rates; the forecast takes
min(target, sum of well capacities at the minimum wellhead pressure).
What ships with it
12 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/two_tank_field.py 2.6 KB runs code
- pyproject.toml 624 B
- README.md 527 B
- src/reservoir_history_match/__init__.py 1003 B runs code
- src/reservoir_history_match/core.py 8.0 KB runs code
- src/reservoir_history_match/field.py 6.4 KB runs code
- src/reservoir_history_match/forecast.py 4.5 KB runs code
- src/reservoir_history_match/handoff.py 3.9 KB runs code
- src/reservoir_history_match/match.py 8.7 KB runs code
- src/reservoir_history_match/prep.py 3.7 KB runs code
- tests/test_history_match.py 6.4 KB runs code
- tests/test_prep.py 1.6 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.
- 27d ago Changed · +24 lines db583b32f9bf
- 1mo ago First seen · 134 lines · 95 tokens per session scan A 7672320e77d0
neqsim-reservoir-history-match-forecast is a skill published in the GitHub repository equinor/neqsim-community-skills (4 stars, last pushed today), licensed Apache-2.0. It adds 95 tokens to every session and 2,424 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-07.
neqsim-reservoir-history-match-forecast compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| neqsim-reservoir-history-match-forecastequinor/neqsim-community-skills | Skill | 4 | today | Apache-2.0 | A | 95 | 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 |