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 uncertainty-quantificationgit 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/uncertainty-quantification)<a href="https://agentmods.dev/skills/equinor/neqsim-community-skills/uncertainty-quantification"><img src="https://agentmods.dev/badge/skills/equinor/neqsim-community-skills/uncertainty-quantification/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/uncertainty-quantification"><img src="https://agentmods.dev/badge/skills/equinor/neqsim-community-skills/uncertainty-quantification.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.00278 | $0.03794 |
| Opus 5 | $0.00139 | $0.01897 |
| Sonnet 5 | $0.00056 | $0.00759 |
| Haiku 4.5 | $0.00028 | $0.00379 |
Grade A, and why
neqsim-uncertainty-quantification 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 10d 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 — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Uncertainty Quantification
A Standard or Comprehensive NeqSim task must report P10/P50/P90 and a tornado diagram. In practice that gets written from scratch in every notebook, and the same four defects recur: sampling that clusters because it is plain pseudo-random at n = 200, a Monte Carlo loop that re-solves the flowsheet for a gas price that never touches it, no check that the run converged, and a tornado presented as if it were a sensitivity analysis when it cannot see interaction.
This skill supplies the sampling, the statistics, the caching, the convergence gate and the report block. It does not own the model — the task supplies that.
When to Use
- A task must produce
uncertaintyforresults.json: P10/P50/P90, mean, standard deviation, probability of a negative outcome, tornado. - A Monte Carlo loop wraps an expensive NeqSim flowsheet and the evaluation budget is the binding constraint.
- Parameters must be screened before a sensitivity budget is committed.
- An interaction between uncertain inputs is suspected and a tornado is not enough.
- An existing uncertainty block must be audited: enough samples, converged, correct percentile convention?
When Not to Use
- As an optimiser. Searching for the best setpoints is
neqsim-optimization-and-doe; this skill propagates uncertainty through a fixed design. - To invent input ranges. A distribution with no basis produces a precise answer to an arbitrary question — record where each range came from.
- For correlated inputs. Every marginal is sampled independently; correlation between, say, price and cost inflation is not represented.
- As a substitute for a risk register. A probability distribution on an output is not a hazard assessment.
Inputs
| Input | Meaning |
|---|---|
parameters |
list of Distribution objects, each with name, unit, kind |
kind |
"technical" (drives the expensive stage) or "economic" (cheap stage only) |
model |
f(values) -> float, for a single-stage study |
technical / economic |
the two-stage split: g(technical) -> intermediate, h(intermediate, economic) -> float |
sampling_method |
"lhs" (default), "random", or "halton" |
seed |
integer for reproducibility |
n |
sample count; at least 200 for a simulation-backed run |
What ships with it
19 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/global_sensitivity_with_salib.py 2.3 KB runs code
- examples/monte_carlo_npv_study.py 2.1 KB runs code
- pyproject.toml 691 B
- README.md 1.8 KB
- src/uncertainty_quantification/__init__.py 2.3 KB runs code
- src/uncertainty_quantification/backends.py 8.2 KB runs code
- src/uncertainty_quantification/distributions.py 8.3 KB runs code
- src/uncertainty_quantification/models.py 5.2 KB runs code
- src/uncertainty_quantification/report.py 6.0 KB runs code
- src/uncertainty_quantification/sampling.py 3.8 KB runs code
- src/uncertainty_quantification/study.py 7.4 KB runs code
- src/uncertainty_quantification/summary_stats.py 5.0 KB runs code
- tests/test_distributions.py 4.5 KB runs code
- tests/test_staged_models.py 2.7 KB runs code
- tests/test_summary_stats.py 3.4 KB runs code
- tests/test_uncertainty_report.py 4.5 KB runs code
- tests/test_uncertainty_study.py 6.2 KB runs code
- tests/test_uq_backends.py 4.1 KB runs code
- tests/test_uq_sampling.py 2.5 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.
- 10d ago First seen · 297 lines · 278 tokens per session scan A 2e6ac00e749f
neqsim-uncertainty-quantification is a skill published in the GitHub repository equinor/neqsim-community-skills (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 278 tokens to every session and 3,794 once invoked, about $0.0014 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…