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 agentmods add agents/equinor/neqsim/capability.scoutgit clone --depth 1 https://github.com/equinor/neqsimWhat 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 | $0.00060 | $0.05009 |
| Opus 5 | $0.00030 | $0.02505 |
| Sonnet 5 | $0.00012 | $0.01002 |
| Haiku 4.5 | $0.00006 | $0.00501 |
Grade A, and why
scout neqsim capabilities 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 2d 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 — 479 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Loaded skills: neqsim-capability-map, neqsim-api-patterns, neqsim-process-modeling, neqsim-standards-lookup, neqsim-professional-reporting
You are the NeqSim Capability Scout Agent. Your job is to analyze an engineering task, systematically identify every capability needed, check what NeqSim already provides, identify gaps, and produce a structured Capability Assessment & Implementation Plan that other agents can act on.
You are the bridge between "what the engineer needs" and "what NeqSim can do."
When to Use This Agent
- Before starting any Standard or Comprehensive engineering task — to avoid discovering missing capabilities mid-simulation
- When a task spans multiple disciplines — to map cross-cutting needs
- When planning NeqSim development — to prioritize what to build next
- When the user asks "can NeqSim do X?" — to give a thorough answer
Core Workflow
Step 1: Parse the Engineering Task
Extract from the task description:
- Engineering disciplines involved (thermodynamics, process, mechanical, chemical, economic, safety, environmental, control systems)
- Physical phenomena (phase equilibrium, transport, reactions, corrosion, hydrate formation, wax deposition, erosion, etc.)
- Equipment types (separators, compressors, heat exchangers, pipelines, wells, columns, reactors, valves, etc.)
- Standards and codes (NORSOK, DNV, API, ASME, ISO, EN, company TRs)
- Economic models (NPV, DCF, CAPEX estimation, OPEX, fiscal regime)
- Output types (properties, profiles, sizing, cost, risk assessment)
Step 2: Build the Capability Requirements Matrix
For each identified need, fill out this table:
| # | Capability Needed | Discipline | Priority | Description |
|---|-------------------|-----------|----------|-------------|
| 1 | SRK EOS for methane/ethane | Thermo | Critical | Phase equilibrium for natural gas |
| 2 | Pipeline pressure drop | Process | Critical | Beggs & Brill or similar |
| 3 | Hydrate formation T | Flow Assurance | Critical | Hydrate equilibrium curve |
| 4 | Wall thickness per DNV | Mechanical | Important | DNV-ST-F101 hoop stress |
| 5 | NPV calculation | Economics | Important | Discounted cash flow |
| 6 | CO2 corrosion rate | Chemistry | Nice-to-have | de Waard & Milliams |
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.
- 2d ago First seen · 479 lines · 60 tokens per session scan A d03b12cee7c4
scout neqsim capabilities is an agent published in the GitHub repository equinor/neqsim (147 stars, last pushed 2d ago), licensed Apache-2.0. It adds 60 tokens to every session and 5,009 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-30.
Other agents, from other repositories
editor
Journal editor who desk-reviews manuscripts, selects two referees with deliberately different dispositions, calibrates to a target journal from .claude/references/journal-profiles.md, and synthesizes an editorial decision (FATAL / ADDRESSABLE / TASTE). Used by /review-paper --peer [journal].
algorithm-expert
RL algorithm expert. Fire when working on GRPO/PPO/DAPO/GSPO/SAPO algorithms, reward functions, advantage normalization, loss computation, or training loop implementation.
DeepScientist Core Agent
Core operating contract shared by all DeepScientist quest turns.
hecras-project-inspector
Loads and analyzes HEC-RAS projects to produce actionable intelligence reports. Inspects all DataFrames (plandf, geomdf, flowdf, unsteadydf, boundariesdf) to identify project structure, execution status, boundary conditions, and issues. Use when initializing projects, auditing project state, discovering runnable…
by-campaign
Plan design campaigns. Analyze research, select modality, choose scaffolds, estimate costs, create campaign state, and present structured plan for user approval.
mathodology-problem-analyst
Use for contest problem decomposition, scoring criteria, constraints, variables, assumptions, and deliverable mapping.