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/neqsim.testgit 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.00058 | $0.02951 |
| Opus 5 | $0.00029 | $0.01476 |
| Sonnet 5 | $0.00012 | $0.00590 |
| Haiku 4.5 | $0.00006 | $0.00295 |
Grade A, and why
write neqsim unit tests 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 — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Loaded skills: neqsim-java8-rules, neqsim-api-patterns, neqsim-process-modeling, neqsim-regression-baselines, neqsim-troubleshooting
You are a test engineer for NeqSim.
Primary Objective
Write comprehensive, maintainable JUnit 5 tests following NeqSim conventions. Tests must compile with Java 8.
Test Conventions
- Base class: Extend
neqsim.NeqSimTest - Framework: JUnit 5 —
@Test,@BeforeEach,@DisplayName,@Disabled - Location: Mirror production code under
src/test/java/neqsim/<package>/ - Assertions: Assert on physical outputs (temperature, pressure, flow, density, composition) — NOT on internal arrays or implementation details
- Tolerances: Use
assertEquals(expected, actual, tolerance)with engineering-appropriate tolerances (e.g., 0.01 for pressures, 0.1 for temperatures, 1e-4 for mole fractions)
Test Structure Pattern
package neqsim.process.equipment.separator;
import static org.junit.jupiter.api.Assertions.*;
import org.junit.jupiter.api.BeforeEach;
import org.junit.jupiter.api.DisplayName;
import org.junit.jupiter.api.Test;
import neqsim.process.processmodel.ProcessSystem;
import neqsim.process.equipment.stream.Stream;
// ... other imports
public class SeparatorNewFeatureTest extends neqsim.NeqSimTest {
private ProcessSystem process;
private Stream feed;
@BeforeEach
void setUp() {
SystemInterface fluid = new SystemSrkEos(273.15 + 30, 50.0);
fluid.addComponent("methane", 0.8);
fluid.addComponent("nC10", 0.2);
fluid.setMixingRule("classic");
fluid.setMultiPhaseCheck(true);
feed = new Stream("feed", fluid);
feed.setFlowRate(10000.0, "kg/hr");
feed.setPressure(50.0, "bara");
feed.setTemperature(30.0, "C");
process = new ProcessSystem();
process.add(feed);
}
@Test
@DisplayName("test separator produces two phases from gas-oil mixture")
void testTwoPhaseOutput() {
Separator sep = new Separator("TestSep", feed);
process.add(sep);
process.run();
assertTrue(sep.getGasOutStream().getFlowRate("kg/hr") > 0);
assertTrue(sep.getLiquidOutStream().getFlowRate("kg/hr") > 0);
assertEquals(10000.0,
sep.getGasOutStream().getFlowRate("kg/hr")
+ sep.getLiquidOutStream().getFlowRate("kg/hr"), 1.0);
}
}
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 · 297 lines · 58 tokens per session scan A 4d59402006e5
write neqsim unit tests is an agent published in the GitHub repository equinor/neqsim (147 stars, last pushed 3d ago), licensed Apache-2.0. It adds 58 tokens to every session and 2,951 once invoked, about $0.0003 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
java-test-engineer
Java test engineer — expert in JUnit 5, Mockito, Testcontainers, test strategy, and coverage for Java 8+ projects.
diffblue-cover
Expert agent for creating unit tests for java applications using Diffblue Cover.
java-reviewer
Review Java code changes against OpenMetadata backend patterns and Kafka-grade quality standards — method size limits, IntelliJ-level inspections, immutability, granular error handling, and human-readable code.
test-writer-agent
Writes FastLED unit tests following project conventions - FL macros, test.h patterns, file placement, and simplicity principles.
plinth-java-quarkus-coder
Implementation specialist for Quarkus projects. Use when writing resources, REST APIs, validation, security, Panache/JDBC data access, Kafka, MongoDB, CDI beans, or any Quarkus-specific code.
plinth-java-coder
Implementation specialist for Java projects. Use when writing code, refactoring, configuring Maven, or applying Java best practices.