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-community-skills --skill skill-templategit clone --depth 1 https://github.com/equinor/neqsim-community-skillsWrote 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-community-skills/skill-template)<a href="https://agentmods.dev/skills/equinor/neqsim-community-skills/skill-template"><img src="https://agentmods.dev/badge/skills/equinor/neqsim-community-skills/skill-template/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-community-skills/skill-template"><img src="https://agentmods.dev/badge/skills/equinor/neqsim-community-skills/skill-template.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.00022 | $0.00455 |
| Opus 5 | $0.00011 | $0.00228 |
| Sonnet 5 | $0.00004 | $0.00091 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
neqsim-your-skill-name 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 9d 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.
What it actually says
Skill Title
One paragraph describing what this public skill helps agents and users do.
When to Use
- When the user asks for ...
- When a task involves ...
Inputs
input_name: units, expected range, and meaning.
Outputs
output_name: meaning and interpretation.
Engineering Method
Describe the public method, assumptions, and boundaries. State clearly whether this is educational screening logic or a validated NeqSim workflow.
Python Usage Pattern
# Add a minimal, tested usage pattern here.
Validation Checklist
- Inputs are validated.
- Examples use public data only.
- Tests cover normal and invalid cases.
- Limitations are explicit.
- NeqSim-dependent behavior has a fallback or clear prerequisite.
Common Mistakes
| Symptom | Cause | Fix |
|---|---|---|
| Example mistake | Why it happens | How to avoid it |
Limitations
- No confidential data or proprietary methods are included.
- State what this skill must not be used for.
Related NeqSim Functionality
Link this skill to NeqSim functionality where possible:
- NeqSim Java classes/methods this skill maps to, for example
neqsim.thermodynamicoperations.ThermodynamicOperations#TPflash(). - NeqSim MCP tools, if applicable.
- How NeqSim is reached, for example
from neqsim import jneqsim. - If the skill only supplies or renders data, name the downstream NeqSim Java/MCP workflow it feeds instead of claiming it runs calculations. Only cite functionality that actually exists.
References
- NeqSim repository: https://github.com/equinor/neqsim
- NeqSim Skills Guide: https://github.com/equinor/neqsim/blob/master/docs/integration/skills_guide.md
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 71 lines · 22 tokens per session scan A 6714cf3b0424
neqsim-your-skill-name is a skill published in the GitHub repository equinor/neqsim-community-skills (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 22 tokens to every session and 455 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…