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-maven-version-maintenancegit 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-maven-version-maintenance)<a href="https://agentmods.dev/skills/equinor/neqsim/neqsim-maven-version-maintenance"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/neqsim-maven-version-maintenance/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-maven-version-maintenance"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/neqsim-maven-version-maintenance.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.00046 | $0.00728 |
| Opus 5.5 | $0.00018 | $0.00291 |
| Sonnet 5.5 | $0.00009 | $0.00146 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
neqsim-maven-version-maintenance 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 today.
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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NeqSim Maven Version Maintenance
Use this workflow when changing a library dependency or Maven plugin version in
either project POM. Treat pom.xml and pomJava8.xml as a coordinated pair;
they build the same project for different runtime baselines and can require
different versions.
Workflow
-
Inspect the current worktree and both POMs before editing. Preserve unrelated user changes. Identify the dependency or plugin coordinates, scope, and current version in each file. Do not assume the two files currently match.
-
Establish the intended version from the request or a trustworthy release source. For an update scan, query both POMs independently:
./mvnw -f pom.xml versions:display-dependency-updates ./mvnw -f pom.xml versions:display-plugin-updates ./mvnw -f pomJava8.xml versions:display-dependency-updates ./mvnw -f pomJava8.xml versions:display-plugin-updatesTreat reported versions as candidates, not automatic recommendations. Check the target artifact's runtime requirements and release notes, especially before changing Java 8 pins. Do not claim Java 8 support from the compiler's
source/targetsettings alone. -
Make the requested changes in both POMs in one edit. Keep versions equal when both runtime baselines support the same release; otherwise use the newest verified Java 8-compatible version in
pomJava8.xmland document the reason in a concise XML comment only when that exception is not already explained nearby. Keep dependency scopes and plugin configuration intentional. -
Compare the resulting declarations by Maven coordinates. Check that an add, removal, or scope change is reflected in both POMs unless the difference is deliberate and explained. Do not modify unrelated plugin, dependency, or project versions as part of a narrow update.
-
Resolve and validate each configuration separately:
./mvnw -f pom.xml validate ./mvnw -f pomJava8.xml validate
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.
- today First seen · 63 lines · 46 tokens per session scan A 59d2fc289a1f
neqsim-maven-version-maintenance is a skill published in the GitHub repository equinor/neqsim (156 stars, last pushed today), licensed Apache-2.0. It adds 46 tokens to every session and 728 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-17.
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…