Borrowing it
Nothing to install: this file belongs to equinor/neqsim. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/equinor/neqsim/master/.github/instructions/neqsim-calculation-routing.instructions.mdgit 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/instructions/equinor/neqsim/neqsim-calculation-routing)<a href="https://agentmods.dev/instructions/equinor/neqsim/neqsim-calculation-routing"><img src="https://agentmods.dev/badge/instructions/equinor/neqsim/neqsim-calculation-routing/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/instructions/equinor/neqsim/neqsim-calculation-routing"><img src="https://agentmods.dev/badge/instructions/equinor/neqsim/neqsim-calculation-routing.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.00884 | $0.00884 |
| Opus 5.5 | $0.00354 | $0.00354 |
| Sonnet 5.5 | $0.00177 | $0.00177 |
| Haiku 4.5 | $0.00088 | $0.00088 |
Grade A, and why
neqsim neqsim-calculation-routing.instructions.md 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Answering a NeqSim calculation request
Prefer the MCP tool for a one-off calculation
A single property, flash, phase-envelope, sizing, PVT, or standards lookup is
served by a curated mcp_neqsim_* tool when the NeqSim MCP server is available.
Use it first: it needs no local Python, no terminal, and no Java, and it returns
a schema-checked result with provenance. Write Python or Java only when the task
needs loops, plotting, a notebook, a report, or state inspected between steps.
Calculate methane density at 20 C and 20 bara
-> mcp_neqsim_runFlash {"components":"{\"methane\": 1.0}", "eos":"SRK",
"flashType":"TP", "temperature":20, "temperatureUnit":"C",
"pressure":20, "pressureUnit":"bara"}
Java is often installed but hidden — find it, do not give up
JVMNotFoundException, "No JVM shared library file (jvm.dll) found", or a JPype
failure on import neqsim usually means the JVM is not discoverable, not that
Java is missing. On managed corporate machines Java is regularly installed with
no java on PATH and no JAVA_HOME.
Do not hand-scan C:\Program Files and do not tell the user to install a JDK
before checking. Run the locator, which searches vendor installs, the user
profile, the Windows registry, and the JRE bundled with the VS Code Java
extension:
uv run --project devtools --locked devtools/java_locator.py # source checkout: lists every usable Java
neqsim doctor # pip install of the CLI: names the found Java
If neqsim is not on PATH, run python -m neqsim_cli doctor with the same
arguments. With only the agent plugin installed (no checkout, no CLI) neither
command exists — but the plugin's session hook resolves a JDK 21+ for the MCP
server on its own, so the mcp_neqsim_* tools still work and remain the route
to prefer.
In Python, make a hidden JVM usable for the current process before touching JPype or NeqSim:
import neqsim_dev_setup, sys, pathlib
sys.path.insert(0, str(pathlib.Path(neqsim_dev_setup.__file__).parent))
from java_locator import ensure_java_home
ensure_java_home() # sets JAVA_HOME + PATH for this process only
import neqsim
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 · +7 tokens per session 845640252e7f
- 16d ago Changed · +13 lines · +201 tokens per session 8c88df71690b
- 1mo ago First seen · 66 lines · 676 tokens per session scan A e8ca2a78457b
neqsim neqsim-calculation-routing.instructions.md is an instructions file published in the GitHub repository equinor/neqsim (158 stars, last pushed today), licensed Apache-2.0. It adds 884 tokens to every session, about $0.0035 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-23.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.