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-code-hygienegit 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-code-hygiene)<a href="https://agentmods.dev/skills/equinor/neqsim/neqsim-code-hygiene"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/neqsim-code-hygiene/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-code-hygiene"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/neqsim-code-hygiene.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.00120 | $0.02817 |
| Opus 5.5 | $0.00048 | $0.01127 |
| Sonnet 5.5 | $0.00024 | $0.00563 |
| Haiku 4.5 | $0.00012 | $0.00282 |
Grade A, and why
neqsim-code-hygiene 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 — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NeqSim Code Hygiene: Formatting, Checkstyle, Spotless & JavaDoc Fixes
This skill is the fix-it playbook for the code-quality gates that fail NeqSim CI:
spotless:check (formatting), checkstyle:check (style, imports, JavaDoc structure),
and javadoc:javadoc (HTML5-valid JavaDoc). It maps each recurring error message to
its exact cause and fix, and gives the mandatory verify loop. For the separate rule
set on which Java language features are allowed, load neqsim-java8-rules.
When to Use This Skill
- The build fails on
spotless:check,checkstyle:check, orjavadoc:javadoc. - A PR or the Problems panel shows formatting, import-order, or JavaDoc violations.
- You created or edited ANY
.javafile (main, test, or examples) and must make it CI-clean. - You pasted a JavaDoc/error block and asked "fix errors like this".
The Fix-and-Verify Loop (do this every time)
- Format first — Spotless fixes whitespace/indentation but NOT import order or JavaDoc content:
./mvnw spotless:apply - Fix Checkstyle/JavaDoc by hand — imports,
<p>tags, single-line JavaDoc, tables (below). - Verify each gate on the touched files, then the whole set:
./mvnw spotless:check ./mvnw checkstyle:check ./mvnw javadoc:javadoc - Re-run
spotless:applyafter hand edits (JavaDoc edits can change wrapping), thengit add. - NEVER bypass with
git commit --no-verify.
Order matters: hand-fix JavaDoc/imports, then
spotless:applylast so the committed file is both style-correct and formatter-clean.
Spotless
- AI-generated Java is not auto-formatted; a single unformatted file fails the whole CI build.
- Profile: Eclipse
.config/neqsim_formatter.xml(pom.xml), applied tosrc/main/javaandsrc/test/java. spotless:applyfixes: indentation (2 spaces), trailing whitespace, blank lines, brace placement, line wrapping of long method chains and string concatenations.spotless:applydoes NOT fix: import ordering, JavaDoc content/structure, unused variables.- Convenience wrapper also available:
uv run --project devtools --locked devtools/run_spotless.py/devtools/run_spotless.sh.
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 Changed b1c52382750f
- 28d ago First seen · 269 lines · 120 tokens per session scan A 8ca046725429
neqsim-code-hygiene is a skill published in the GitHub repository equinor/neqsim (156 stars, last pushed today), licensed Apache-2.0. It adds 120 tokens to every session and 2,817 once invoked, about $0.0005 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-19.
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…