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-heat-integrationgit 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-heat-integration)<a href="https://agentmods.dev/skills/equinor/neqsim/neqsim-heat-integration"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/neqsim-heat-integration/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-heat-integration"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/neqsim-heat-integration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium analysis-evasion · line 1 Suspicious Unicode normalization or mixed-script contentFix: Review the flagged content for security risks. Ensure no credentials, secrets, or sensitive data are exposed.
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.00078 | $0.01530 |
| Opus 5.5 | $0.00031 | $0.00612 |
| Sonnet 5.5 | $0.00016 | $0.00306 |
| Haiku 4.5 | $0.00008 | $0.00153 |
Grade A, and why
neqsim-heat-integration 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 6d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NeqSim Heat Integration Skill
Linnhoff-method pinch analysis to determine minimum hot/cold utility duties, the pinch temperature, composite & grand-composite curves, and to evaluate heat-exchanger network (HEN) opportunities.
When to Use
- Determining MER (Minimum Energy Requirement) for a flowsheet
- Setting utility duties before equipment sizing
- Retrofit analysis — quantify potential savings vs. existing HEN
- Comparing process alternatives on energy footprint
- Sizing utility headers (steam, cooling water) consistently across a plant
Standard reference: B. Linnhoff & E. Hindmarsh (1983), Chem. Eng. Sci.; operational guidance from Smith — Chemical Process Design and Integration (2nd ed.).
Core Concept
Hot streams (need cooling) ──┐
├── shifted by ΔTmin/2 → temperature intervals → cascade → MER
Cold streams (need heating) ──┘
The pinch divides the system in two:
- Above pinch — heat sink (only hot utility allowed)
- Below pinch — heat source (only cold utility allowed)
- Across pinch — every kW transferred costs 1 kW hot + 1 kW cold
Three golden rules — never violate any of them:
- No external heating below the pinch
- No external cooling above the pinch
- No heat transfer across the pinch
Pattern 1 — Streams Defined Manually
import neqsim.process.equipment.heatexchanger.heatintegration.PinchAnalysis;
PinchAnalysis pinch = new PinchAnalysis(10.0); // ΔTmin in °C
// addHotStream(name, supplyT_C, targetT_C, mCp_kW_per_K)
pinch.addHotStream("H1 — reactor effluent", 180.0, 80.0, 30.0);
pinch.addHotStream("H2 — flash gas", 150.0, 50.0, 15.0);
pinch.addColdStream("C1 — feed preheat", 30.0, 140.0, 20.0);
pinch.addColdStream("C2 — reboiler feed", 60.0, 120.0, 25.0);
pinch.run();
double Qh = pinch.getMinimumHeatingUtility(); // kW
double Qc = pinch.getMinimumCoolingUtility(); // kW
double Tpinch = pinch.getPinchTemperatureC();
Pattern 2 — Auto-Extract from a ProcessSystem
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.
- 6d ago Changed bd0ce657efa6
- 1mo ago First seen · 135 lines · 78 tokens per session scan A 5a8131f5c462
neqsim-heat-integration is a skill published in the GitHub repository equinor/neqsim (156 stars, last pushed today), licensed Apache-2.0. It adds 78 tokens to every session and 1,530 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-09-03.
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…