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 --skill neqsim-unisim-readergit 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/skills/equinor/neqsim/neqsim-unisim-reader)<a href="https://agentmods.dev/skills/equinor/neqsim/neqsim-unisim-reader"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/neqsim-unisim-reader/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/neqsim-unisim-reader"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/neqsim-unisim-reader.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium analysis-evasion · line 1 Suspicious Unicode normalization or mixed-script contentFix: Review the flagged content for security risks. Ensure no credentials, secrets, or sensitive data are exposed.
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.00096 | $0.24022 |
| Opus 5.5 | $0.00038 | $0.09609 |
| Sonnet 5.5 | $0.00019 | $0.04804 |
| Haiku 4.5 | $0.00010 | $0.02402 |
Grade A, and why
neqsim-unisim-reader 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 8d 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 — 1,938 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UniSim Design / HYSYS → NeqSim Conversion Skill
Convert Honeywell UniSim Design (.usc) files into NeqSim ProcessSystem or ProcessModule structures using Windows COM automation.
Prerequisites
- Windows only — UniSim Design must be installed (COM server)
- Python packages:
pywin32(pip install pywin32) - UniSim Design R510+ (R460+ should also work)
- COM ProgID:
UnisimDesign.Application
Core Module
The devtools/unisim_reader.py module provides three main classes:
| Class | Purpose |
|---|---|
UniSimReader |
Opens .usc files via COM, extracts all data |
UniSimToNeqSim |
Converts extracted model to NeqSim JSON builder format or standalone Python code |
UniSimComparator |
Compares UniSim vs NeqSim results for verification |
Supporting tools:
| Tool | Purpose |
|---|---|
devtools/unisim_batch_check.py |
Convert a whole corpus, one subprocess per case; timings, unmapped types, warnings, compile + undefined-name checks |
devtools/unisim_run_generated.py |
Execute every generated model in its own subprocess and report how far it gets |
devtools/unisim_probe_ops.py |
Dump the readable COM properties of an operation type |
devtools/unisim_probe_column.py |
Dump a column's attached streams and ColumnFlowsheet internals |
devtools/test_unisim_outputs.py |
Pure-Python regression tests (no COM needed) |
1. UniSim COM Object Model
UniSim's COM automation exposes the following hierarchy:
Application
├── SimulationCases
│ └── Case
│ ├── Solver (CanSolve, Converge)
│ ├── BasisManager
│ │ └── FluidPackages[]
│ │ ├── name, PropertyPackageName
│ │ └── Components[]
│ │ └── name
│ └── Flowsheet (main)
│ ├── MaterialStreams[]
│ │ ├── name
│ │ ├── Temperature.GetValue("C")
│ │ ├── Pressure.GetValue("bar")
│ │ ├── MassFlow.GetValue("kg/h")
│ │ ├── MolarFlow.GetValue("kgmole/h")
│ │ ├── MassDensity.GetValue("kg/m3")
│ │ ├── MolecularWeight.GetValue()
│ │ ├── VapourFraction.GetValue()
│ │ ├── MassEnthalpy.GetValue("kJ/kg")
│ │ ├── ComponentMolarFraction.GetValues()
│ │ └── ComponentMolarFraction.SetValues([...])
│ ├── EnergyStreams[]
│ │ ├── name
│ │ └── HeatFlow.GetValue("kW")
│ ├── Operations[]
│ │ ├── name, TypeName
│ │ ├── Feeds[] (multi-feed ops: mixers, separators)
│ │ ├── Products[] (multi-product ops: tee/splitter)
│ │ ├── FeedStream / ProductStream (single-stream ops)
│ │ ├── Product (singular, for mixers)
│ │ ├── VapourProduct, LiquidProduct, WaterProduct (separators)
│ │ ├── EnergyFeeds[], EnergyProducts[]
│ │ └── Type-specific: DutyValue, AdiabaticEfficiency,
│ │ PolytropicEfficiency, PressureDrop, Length, Diameter
│ └── Flowsheets[] (sub-flowsheets, recursive)
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.
- 8d ago Changed aa0824e9b222
- 28d ago Changed · -15 tokens per session 1a4514c7964a
- 1mo ago Changed · +228 lines · +17 tokens per session a25e9dec3bdb
- 1mo ago Changed · +79 lines 1a68d43040ce
- 1mo ago First seen · 1,631 lines · 94 tokens per session scan A 546d05828c3f
neqsim-unisim-reader is a skill published in the GitHub repository equinor/neqsim (158 stars, last pushed today), licensed Apache-2.0. It adds 96 tokens to every session and 24,022 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-09-03.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.