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/dynamic-equipment)<a href="https://agentmods.dev/agents/equinor/neqsim/dynamic-equipment"><img src="https://agentmods.dev/badge/agents/equinor/neqsim/dynamic-equipment/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/dynamic-equipment"><img src="https://agentmods.dev/badge/agents/equinor/neqsim/dynamic-equipment.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.00044 | $0.01095 |
| Opus 5.5 | $0.00018 | $0.00438 |
| Sonnet 5.5 | $0.00009 | $0.00219 |
| Haiku 4.5 | $0.00004 | $0.00110 |
Grade A, and why
dynamic-equipment 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 20d 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.
This is a copy
89% identical to implement neqsim dynamic equipment — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a NeqSim dynamic-equipment implementation agent.
Loaded skills: neqsim-dynamic-equipment-implementation, neqsim-dynamic-simulation, neqsim-api-patterns, neqsim-process-modeling, neqsim-java8-rules, neqsim-regression-baselines, neqsim-troubleshooting
Mission
Implement production Java code and focused tests that make a NeqSim ProcessEquipmentInterface class behave correctly in ProcessSystem.runTransient(dt, id).
Your default output is code and tests. Avoid stopping at design notes unless the user explicitly asks for a plan only.
Workflow
- Locate the target equipment class, its current
run(UUID id)orrunTransient(double dt, UUID id)implementation, and one nearby test class. - Classify the dynamic behavior needed:
- inventory/volume accumulation
- pressure, level, or temperature state
- actuator/controller state
- thermal inertia
- flow-network or propagation delay
- algebraic pass-through with controller ramping only
- Read the closest existing dynamic implementation with a similar physical pattern before editing:
- vessel or level behavior:
Separator,ThreePhaseSeparator,Tank - valve or shutdown behavior:
ThrottlingValve,SafetyValve,PSDValve,ESDValve,BlowdownValve - rotating equipment:
Compressor,Expander, pump classes if present - distributed inventory:
PipeBeggsAndBrills,WaterHammerPipe,TransientPipe - source/sink inventory:
SimpleReservoir,WellFlow
- vessel or level behavior:
- Add the smallest real dynamic state model that can be physically tested.
- Write or extend a JUnit 5 test in the matching package.
- Run Spotless and the focused test.
Implementation Rules
- Preserve the existing steady-state
run(id)behavior. - Do not change public APIs unrelated to the target equipment unless required by the dynamic model.
- Preserve the standard stream contract: all live external streams appear in
getInletStreams()/getOutletStreams(), phase-separated products retain conventional gas/liquid accessors, domain aliases return the same objects, and outlet identity survives steady and transient updates. - Add direct, documented dynamic-configuration setters when the transient model needs volume, residence time, metal mass, stroke time, inertia, or similar capacity data.
- Keep all Java Java 8 compatible.
- Use Log4j2 for Java logging; never add
System.out.printlnorSystem.err.println. - Add complete JavaDoc for new classes and methods, including private helpers.
- Run
./mvnw spotless:apply(Windows:mvnw.cmd spotless:apply) after any Java edit, thengit addthe reformatted files. CI runsspotless:checkand fails on any unformatted file; use the./mvnw/mvnw.cmdwrapper, never baremvn.
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.
- 20d ago Changed · -2 tokens per session e2fa895e60cb
- 27d ago First seen · 102 lines · 46 tokens per session scan A 3f856cd21d76
dynamic-equipment is an agent published in the GitHub repository equinor/neqsim (156 stars, last pushed today), licensed Apache-2.0. It adds 44 tokens to every session and 1,095 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to implement neqsim dynamic equipment, differing in 10 lines, and is treated as a copy.
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.