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-root-cause-analysisgit 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-root-cause-analysis)<a href="https://agentmods.dev/skills/equinor/neqsim/neqsim-root-cause-analysis"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/neqsim-root-cause-analysis/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-root-cause-analysis"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/neqsim-root-cause-analysis.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 Excessive Agency · line 286 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00101 | $0.07284 |
| Opus 5.5 | $0.00040 | $0.02914 |
| Sonnet 5.5 | $0.00020 | $0.01457 |
| Haiku 4.5 | $0.00010 | $0.00728 |
Grade A, and why
neqsim-root-cause-analysis 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 11d 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 — 694 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NeqSim Root Cause Analysis Skill
Systematic equipment-level root cause analysis integrating process simulation, multi-source reliability data, plant historian time-series, and STID design conditions.
When to Use
- Equipment trip investigation (compressor, pump, turbine)
- High vibration diagnosis
- Efficiency degradation analysis
- Separator liquid carryover or gas blow-by
- Heat exchanger fouling assessment
- Valve erosion or malfunction
- Any operational anomaly requiring structured root cause identification
Already-closed incident with a "document learning" ask
When the failure is already resolved and recorded (for example a closed Blalys whose
only open subtask is to document learning), do not re-derive the cause. Cite the
recorded cause, test it for consistency against the historian and alarm evidence
(consistent, contradicted or not testable), then deliver a consequence and learning
screening: capacity impact (for a derated driver use Compressor.getDriverLimitedEnvelope()),
the barrier or early indicator that would have shortened the outage, and the cost of
recurrence. Mark causal claims beyond the recorded cause as hypotheses.
Rapid Triage Mode (live disturbance)
A full RCA is a study. When the plant is still down and a response team needs a direction within minutes, run the same framework in a reduced, explicitly labelled mode rather than a different method:
| Full RCA | Rapid triage | |
|---|---|---|
| Prior | Multi-source reliability data | Reliability prior only, no source reconciliation |
| Likelihood | Full historian window, quality-screened | Last stable period to now, unscreened |
| Verification | NeqSim simulation of each hypothesis | Skipped; verification is deferred |
| Output | Ranked hypotheses with confidence | Top 3 candidates, confidence capped at MODERATE |
| Cause claim | Established when evidence supports it | NOT_DETERMINED unless a single candidate dominates |
Rules that make the reduced mode safe to act on:
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.
- 11d ago Changed · +9 lines 7d461afbb5e4
- 12d ago Changed · +28 lines 851bb1e275b5
- 20d ago Changed · -31 tokens per session 3e5b77199855
- 29d ago Changed · +64 lines · +30 tokens per session 8d5f768f2b61
- 1mo ago First seen · 593 lines · 102 tokens per session scan A e53c74c3eb43
neqsim-root-cause-analysis is a skill published in the GitHub repository equinor/neqsim (156 stars, last pushed today), licensed Apache-2.0. It adds 101 tokens to every session and 7,284 once invoked, about $0.0004 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…