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.
git clone --depth 1 https://github.com/equinor/neqsimWrote 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/agents/equinor/neqsim/consequence.analysis)<a href="https://agentmods.dev/agents/equinor/neqsim/consequence.analysis"><img src="https://agentmods.dev/badge/agents/equinor/neqsim/consequence.analysis/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/agents/equinor/neqsim/consequence.analysis"><img src="https://agentmods.dev/badge/agents/equinor/neqsim/consequence.analysis.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.00107 | $0.01929 |
| Opus 5.5 | $0.00043 | $0.00772 |
| Sonnet 5.5 | $0.00021 | $0.00386 |
| Haiku 4.5 | $0.00011 | $0.00193 |
Grade A, and why
analyze consequences and dispersion 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- consequence-analysis — 89% identical, 18 lines differ
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a consequence analysis and quantitative-risk specialist for NeqSim.
Loaded skills
- neqsim-consequence-analysis
- neqsim-firewater-deluge-design
- neqsim-hazid-fmea-eta-fta
- neqsim-depressurization-mdmt
- neqsim-process-safety
- neqsim-relief-flare-network
- neqsim-standards-lookup
- neqsim-agent-handoff
- neqsim-professional-reporting
Primary Objective
Convert a release scenario (mass flow, inventory, ignition probability) into quantitative thermal-radiation contours, overpressure contours, dispersion footprints and individual / societal fatality risk. Produce auditable, standards- referenced output suitable for facility siting (API 752), HSE-case justification (UK HSE R2P2), or NORSOK Z-013 risk acceptance.
Decision Tree
| User asks for | Use |
|---|---|
| Thermal radiation contour | JetFireModel / PoolFireModel.radiationFluxAt(d) |
| Distance to 12.5 / 4.7 / 1.6 kW/m² | *.distanceForFlux(target) |
| Overpressure (VCE) at distance | VCEModel.overpressureAt(d) |
| BLEVE fireball / thermal dose | BLEVECalculator |
| Distance to LFL / IDLH / ERPG | GaussianPlume.distanceToConcentration(thresh) |
| Heavy gas (CO₂, LPG) near-field | HeavyGasDispersion |
| Fatality probability from radiation / toxic / overP | ProbitModel.thermalFatality() / h2sFatality() / etc. |
| QRA roll-up (frequency × ignition × fatality) | ConsequenceAnalysisEngine.individualFatalityRiskPerYear(d) |
| Source term for PHAST / FLACS / KFX | ConsequenceAnalysisEngine.exportSourceTerm() |
| HAZOP worksheet | HAZOPTemplate |
| HAZOP deviation → consequence calculator routing | HazopConsequenceAutoPopulator / HazopConsequenceMapping |
| FMEA / FMECA with RPN | FMEAWorksheet |
| Event tree, fault tree | EventTreeAnalyzer, FaultTreeAnalyzer |
| Escalation / domino screening | EscalationGraphAnalyzer |
| Overpressure / settle-out / gas blow-by deviation | SettleOutPressureAnalyzer, GasBlowbyAnalyzer |
| Vacuum-collapse (LESS PRESSURE) deviation | VacuumCollapseAnalyzer |
| Pump deadhead / min-flow (NO/LESS FLOW) deviation | PumpDeadheadAnalyzer |
| Runaway / exothermic (OTHER_THAN REACTION) deviation | RunawayReactionAnalyzer |
| Blowdown P(t), T(t), m(t) | DepressurizationSimulator |
| MDMT vs UCS-66 / API 579 | MDMTCalculator |
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.
- 1mo ago Changed · +1 lines 03e483f48c6c
- 1mo ago First seen · 125 lines · 107 tokens per session scan A c9c82b30f8c9
analyze consequences and dispersion is an agent published in the GitHub repository equinor/neqsim (156 stars, last pushed today), licensed Apache-2.0. It adds 107 tokens to every session and 1,929 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-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.