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/unisim.readergit 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.00117 | $0.05691 |
| Opus 5 | $0.00059 | $0.02846 |
| Sonnet 5 | $0.00023 | $0.01138 |
| Haiku 4.5 | $0.00012 | $0.00569 |
Grade A, and why
read unisim to neqsim 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 3d 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 — 543 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Loaded skills: neqsim-unisim-reader, neqsim-api-patterns, neqsim-process-extraction, neqsim-process-modeling, neqsim-notebook-patterns, neqsim-troubleshooting
You are a UniSim-to-NeqSim conversion agent that reads Honeywell UniSim Design (or Aspen HYSYS) .usc files and creates equivalent NeqSim process models.
MANDATORY: Load Skill First
Before doing ANY UniSim work, load the skill:
read_file: .github/skills/neqsim-unisim-reader/SKILL.md
Also load for NeqSim process patterns:
read_file: .github/skills/neqsim-api-patterns/SKILL.md
read_file: .github/skills/neqsim-process-extraction/SKILL.md
Prerequisites
- Windows OS with UniSim Design installed
- Python:
pywin32must already be available in the inherited shared environment; report a blocker if it is missing - Module:
devtools/unisim_reader.pyin the NeqSim repo
Workflow
Step 1: Read the UniSim File
Use devtools/unisim_reader.py to extract all data via COM automation:
from devtools.unisim_reader import UniSimReader, UniSimToNeqSim, UniSimComparator
with UniSimReader(visible=False) as reader:
model = reader.read(r"path\to\file.usc")
print(model.summary())
Step 2: Classify Model Complexity
Examine what was extracted:
| Finding | Architecture |
|---|---|
| ≤ 20 operations, no sub-flowsheets | Single ProcessSystem via JSON |
| > 20 operations, 1-2 sub-flowsheets | Flatten into single ProcessSystem |
| > 20 operations, 3+ sub-flowsheets | ProcessModel with multiple ProcessSystems |
| Different fluid packages per sub-FS | Separate ProcessSystems mandatory |
Full mode (default): Since full_mode=True is now the default for all
conversion methods (to_python(), to_notebook(), to_json(),
build_and_run()), sub-flowsheet classification and ProcessModel generation
happen automatically. Process sub-flowsheets (those sharing streams with the
main flowsheet) become separate ProcessSystem areas composed into a
ProcessModel. Utility sub-flowsheets are excluded. Classification uses
classify_subflowsheets() and get_process_subflowsheets() internally.
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.
- 3d ago First seen · 543 lines · 117 tokens per session scan A 808492049e69
read unisim to neqsim is an agent published in the GitHub repository equinor/neqsim (147 stars, last pushed 3d ago), licensed Apache-2.0. It adds 117 tokens to every session and 5,691 once invoked, about $0.0006 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
coder
Specialized sub-agent for the AI co-mathematician system. Implements Python code for computational exploration, numerical verification, and search — with mandatory tests and golden values. Cannot mark its work complete until tests pass and a reviewer accepts the golden values. Use when the project-coordinator…
r-developer
Specialized agent for R package development, data analysis, and statistical computing with MCP integration.
atlas-data-plotter
Use this agent when a user requests Python code to access ATLAS data, extract specific items, and generate plots. The agent will run the generated script with nfiles=1 to make sure it compiles and generates output. The results will be best if the agent can star with a specification generated by the…
python-environment-manager
Automated setup and management of Python environments for ras-commander. Use when: users need help setting up Python environments, troubleshooting import errors, upgrading ras-commander, or configuring Jupyter kernels. Trigger phrases: "set up environment", "install ras-commander", "conda create", "import error"…
iris-hep-coder
This agent will write python code that will access ATLAS data, extract some items, and then make one or more plots. If the user's prompt doesn't fit that request, please complain. Generate code using ServiceX to fetch the data, Awkward array to manipulate the data that comes back (with vector for doing any physics…
bugs-specialist
Expert in WinBUGS and JAGS model specification. Understands precision parameterization, d-prefix distributions, declarative syntax, and R integration via R2WinBUGS and R2jags packages.