Borrowing it
Nothing to install: this file belongs to equinor/neqsim. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/equinor/neqsim/master/.github/skills/neqsim-version-bump-decision/SKILL.mdgit 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-version-bump-decision)<a href="https://agentmods.dev/skills/equinor/neqsim/neqsim-version-bump-decision"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/neqsim-version-bump-decision/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-version-bump-decision"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/neqsim-version-bump-decision.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.00049 | $0.00962 |
| Opus 5.5 | $0.00020 | $0.00385 |
| Sonnet 5.5 | $0.00010 | $0.00192 |
| Haiku 4.5 | $0.00005 | $0.00096 |
Grade A, and why
neqsim-version-bump-decision 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 2d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NeqSim Version Bump Decision
Scope
Use this skill for the NeqSim project's own release version, not dependency or
Maven plugin versions. For dependency/plugin upgrades, use
neqsim-maven-version-maintenance.
This skill recommends patch or minor. It does not decide or apply a major
version, create a GitHub release, or publish artifacts.
Decision Rules
| Change | Recommendation | Conditions |
|---|---|---|
| Bug fix, refactor, or performance correction | Patch | No public API/capability addition or incompatible API change; serialization gate below passes. |
| New backward-compatible capability or public API | Minor | Existing APIs and serialized state remain compatible. |
| Removed or incompatible public API, incompatible serialized state, or uncertain compatibility | Manual major review | Do not recommend or apply a patch/minor bump as a workaround. A human decides the major version. |
Use SemVer increments from the current released version. For example, from
3.25.0, a patch candidate is 3.25.1 and a minor candidate is 3.26.0.
Do not infer or choose a major version; that decision remains manual. A patch
release does not satisfy the minor-or-major deprecation period in the
API lifecycle policy.
Serialization Compatibility Gate
Patch recommendations require evidence that serialized objects from supported
previous releases remain readable and retain their intended state after loading.
Apply this gate to every affected Serializable class and its serialized object
graph:
- Preserve an explicit
serialVersionUID. If the class relies on a computed UID, compare it with the previous released version; do not assume a source-level refactor leaves it unchanged. - Check serialized field names, types, and meanings, plus any custom
readObject,writeObject,readResolve,writeReplace, orExternalizablebehavior. - A new serialized field is acceptable only when old streams load correctly, its default state is valid, and compatibility is verified. A renamed or retyped field, changed UID, or changed interpretation that prevents correct restoration fails the patch gate.
- Prefer a fixture serialized by a supported released version and test loading it with the candidate code. A same-version round trip alone does not prove cross-version compatibility. Test candidate-to-old-reader compatibility too when that is part of the persistence contract.
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.
- 2d ago First seen · 85 lines · 49 tokens per session scan A ddb06f0c4cf3
neqsim-version-bump-decision is a skill published in the GitHub repository equinor/neqsim (156 stars, last pushed today), licensed Apache-2.0. It adds 49 tokens to every session and 962 once invoked, about $0.0002 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-16.
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…