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-process-synthesis-researchgit 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-process-synthesis-research)<a href="https://agentmods.dev/skills/equinor/neqsim/neqsim-process-synthesis-research"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/neqsim-process-synthesis-research/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-process-synthesis-research"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/neqsim-process-synthesis-research.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.00081 | $0.02990 |
| Opus 5.5 | $0.00032 | $0.01196 |
| Sonnet 5.5 | $0.00016 | $0.00598 |
| Haiku 4.5 | $0.00008 | $0.00299 |
Grade A, and why
neqsim-process-synthesis-research 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 12d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Process Synthesis Research
When to use this
Use ProcessResearcher when the topology is not yet selected and the task starts from a feed composition plus one or more product targets. The package builds a bounded candidate set, prunes invalid routes, optionally runs each candidate through NeqSim's process JSON builder, scores results, and returns ranked candidates with warnings and assumptions.
Use neqsim-optimization-and-doe instead when an existing flowsheet topology is fixed and the question is which setpoints, equipment variables, or operating conditions optimize it. A generated candidate's internal bounded decision-variable grid is a screening layer, not the same as a general external optimizer.
The API is documented in docs/process/optimization/process-researcher.md, and ProcessResearcherTest covers generated candidates, graph paths, the curated conditioning library, pruning, metrics, and exports. No ProcessResearcher-named runner was found under src/main/java/neqsim/mcp; the entry point is the Java API (also reachable through the Java classes exposed by neqsim Python).
What search means here
ProcessCandidateGeneratorcreates candidates from allowed unit types, reaction options, operation options, and optionally curated templates.ProcessSynthesisGraphenumerates bounded material-operation paths usingMaterialNode,OperationOption, and product targets. The test confirms a two-operation compression/separation path is generated asprocess-network-graph.ProcessSynthesisTemplateLibraryadds curated patterns such as compression, aftercooling, and polishing separation when enabled. This is template/path enumeration, not unconstrained flowsheet topology search.ProcessSynthesisFeasibilityPrunerrejects invalid specs and disconnected material paths before simulation.ProcessCandidateEvaluatorruns surviving JSON definitions and may grid-screen decision variables.ProcessResearcherranks/marks candidates using configured product-oriented scoring and reported metrics; it does not call a general MINLP solver to search all unit combinations and continuous variables jointly.ProcessSuperstructureExporteremits a reduced superstructure JSON and a Pyomo/GDP starter skeleton. The skeleton requires a caller-owned formulation, solver, constraints, and validation; NeqSim does not execute the external MINLP for this workflow.
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.
- 12d ago First seen · 154 lines · 81 tokens per session scan A 06950939190d
neqsim-process-synthesis-research is a skill published in the GitHub repository equinor/neqsim (156 stars, last pushed today), licensed Apache-2.0. It adds 81 tokens to every session and 2,990 once invoked, about $0.0003 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-10-05.
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…
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…