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 reservoir-depletion-screeninggit 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/reservoir-depletion-screening)<a href="https://agentmods.dev/skills/equinor/neqsim-community-skills/reservoir-depletion-screening"><img src="https://agentmods.dev/badge/skills/equinor/neqsim-community-skills/reservoir-depletion-screening/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/reservoir-depletion-screening"><img src="https://agentmods.dev/badge/skills/equinor/neqsim-community-skills/reservoir-depletion-screening.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.00070 | $0.01302 |
| Opus 5 | $0.00035 | $0.00651 |
| Sonnet 5 | $0.00014 | $0.00260 |
| Haiku 4.5 | $0.00007 | $0.00130 |
Grade A, and why
neqsim-reservoir-depletion-screening 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 12d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reservoir Depletion Screening
Use this skill for a quick, public screening of how a reservoir develops with
time. Given a recoverable volume, an offtake rate, and an initial and
abandonment pressure, it produces a year-by-year profile of reservoir pressure,
cumulative production, recovery factor, water cut, and hydrocarbon/water rates.
It is intentionally simple and should guide users toward the validated NeqSim
SimpleReservoir tank model (runTransient) and the NeqSim MCP runReservoir
workflow for real depletion behaviour.
When to Use
- When a user wants a first look at how reservoir pressure declines over field life.
- When an early production/decline profile is needed before a reservoir model exists.
- When an agent needs an upstream "reservoir vs time" feed for a production-routing or arrival-pressure screening chain.
Inputs
fluid_type:gasoroil.initial_pressure_bara: reservoir pressure at start of production.abandonment_pressure_bara: pressure at which production stops (screening).recoverable_volume_sm3: recoverable hydrocarbon volume at standard conditions.offtake_rate_sm3_per_day: constant screening offtake (hydrocarbon) rate.years: number of years to simulate.time_step_years: time-step size (default 1.0 year).initial_water_cut_fraction: water cut at start (default 0).water_cut_rise_per_year: linear water-cut rise per year (default 0).
Outputs
steps: per-stepyear,pressure_bara,cumulative_production_sm3,recovery_factor,water_cut_fraction,hydrocarbon_rate_sm3_per_day,water_rate_sm3_per_day, anddepletedflag.final_pressure_bara,final_recovery_factor.plateau_years: years before production can no longer be sustained (orNone).years_to_abandonment: first year the reservoir reaches abandonment (orNone).depletion_warning:ok,watch, orhigh.neqsim_available: whether the optional NeqSim package is importable.assumptions: public assumptions and required follow-up.
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.
- 12d ago First seen · 132 lines · 70 tokens per session scan A 95eb8ed83368
neqsim-reservoir-depletion-screening is a skill published in the GitHub repository equinor/neqsim-community-skills (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 70 tokens to every session and 1,302 once invoked, about $0.0003 per session on Opus 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-08-31.
Other skills, from other repositories
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…