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/dynamic.equipmentgit 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.svg" alt="Measured on agentmods" 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 | $0.00046 | $0.00942 |
| Opus 5 | $0.00023 | $0.00471 |
| Sonnet 5 | $0.00009 | $0.00188 |
| Haiku 4.5 | $0.00005 | $0.00094 |
Grade A, and why
implement neqsim 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 4d 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 — 86 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.cmd spotless:applyafter any Java edit.
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.
- 4d ago First seen · 86 lines · 46 tokens per session scan A e50aad8c6eff
implement neqsim dynamic equipment is an agent published in the GitHub repository equinor/neqsim (150 stars, last pushed today), licensed Apache-2.0. It adds 46 tokens to every session and 942 once invoked, about $0.0002 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
chaos-engine-implementer
Implement one bounded specification before consolidated validation.
chaos-engine
Use for main-thread orchestration covering decomposition, architecture, synthesis, and final verification.
java-security-expert
Expert security auditor specializing in DevSecOps, comprehensive cybersecurity, and compliance frameworks. Masters vulnerability assessment, threat modeling, secure authentication (OAuth2/OIDC), OWASP standards, cloud security, and security automation. Handles DevSecOps integration, compliance (GDPR/HIPAA/SOC2), and…
gcx-java-tester
Test gcx parser quality for Java repos. Clones canonical Java projects, indexes with locally-built gcx, checks node/edge coverage, and flags Java-specific AST issues. Use when validating or debugging the Java parser.
enterprise-code-architect
Designs enterprise Java architecture for re-implementing source projects from any language — adapts stack based on project type (Spring Boot 4 for applications, plain Java 21+ for libraries/frameworks), creates technology mappings with Mermaid visualizations, designs module structure with proper Maven dependency…
java-reviewer
Expert Java and Spring Boot code reviewer specializing in layered architecture, JPA patterns, security, and concurrency. Use for all Java code changes. MUST BE USED for Spring Boot projects.