neqsim-task-workflow

neqsim-task-workflow is a skill for Claude Code from equinor/neqsim. It costs 90 tokens per session (33,899 once invoked), scanned A, original, Apache-2.0.

A step-by-step workflow for completing NeqSim engineering tasks from setup through research, notebooks, validation, and reporting. NeqSim is an engineering simulation tool for studying fluids and thermodynamic processes.

In plain words
What is it for?
Use it to run standard or comprehensive engineering tasks, maintain a reproducibility log, validate notebook results, and assess uncertainty and risk.
Why use it?
It keeps the task scope, user input, assumptions, research, and validation steps recorded so the work can be repeated and checked.

Skill for Claude Code

Written for Claude Code: SessionStart hook event. Also seen: mentions subagents; positional $N argument.

Good fit Use it to run standard or comprehensive engineering tasks, maintain a reproducibility log, validate notebook results, and assess uncertainty and risk.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/equinor/neqsim/neqsim-task-workflow
Install

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.

Any agent
npx skills add equinor/neqsim --skill neqsim-task-workflow
Clone the repo
git clone --depth 1 https://github.com/equinor/neqsim

Made for: Claude Code.

Wrote 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.

agentmods badge for neqsim-task-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/equinor/neqsim/neqsim-task-workflow/github.svg)](https://agentmods.dev/skills/equinor/neqsim/neqsim-task-workflow)
Your own site
<a href="https://agentmods.dev/skills/equinor/neqsim/neqsim-task-workflow"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/neqsim-task-workflow/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.

agentmods 80×15 button for neqsim-task-workflow

Your own site · 80×15
<a href="https://agentmods.dev/skills/equinor/neqsim/neqsim-task-workflow"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/neqsim-task-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 90 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 33,899 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00090 $0.33899
Opus 5.5 $0.00036 $0.13560
Sonnet 5.5 $0.00018 $0.06780
Haiku 4.5 $0.00009 $0.03390

Measured 5d ago against content hash 53be14218f77, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

neqsim-task-workflow 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 5d 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.

.github/skills/neqsim-task-workflow/SKILL.md · 2,529 lines

How it starts

The opening of the file, as written. The whole thing — 2,529 lines — stays where its author put it; the contents beside it link to each section on GitHub.

NeqSim Task Workflow

This is the detailed procedure behind @solve-task. The agent file holds the mandatory first action, the purpose, and the operating principles (section 0); sections 1-10 below are loaded on demand for Standard and Comprehensive work. Section numbers are kept so cross-references from the agent and from docs/development/TASK_SOLVING_GUIDE.md stay valid.


0.5 ── ALWAYS-ON OBLIGATIONS (moved from the agent)

Keep user_input.md up to date through the whole conversation

user_input.md is the reproducibility log — anyone re-running this task should be able to recover the exact starting input from it.

Whenever the user provides new information during the task, append it to user_input.md immediately and verbatim:

  • Answers to your clarifying questions → append to section 2 (Q&A)
  • Mid-task corrections, scope changes, or new constraints → append to section 3 (Follow-up)
  • Any value you assume because the user did not specify it → record it in section 4 (Inferred Assumptions) with justification

Do NOT paraphrase, summarise, or "clean up" the user's wording. Paste it as given. Never delete previous entries — only append.

All downloaded documents go INSIDE the task folder

All documents retrieved during a task — STID drawings, PI historian exports, vendor datasheets, P&IDs, literature PDFs, downloaded standards — MUST be saved to step1_scope_and_research/references/ within the task folder.

NEVER download or save task-related files to workspace-level directories like output/, figures/, or any path outside task_solve/YYYY-MM-DD_slug/.

For STID/document retrieval scripts: Always pass the task's references/ path as the output directory:

# CORRECT — saves inside the task folder:
out_dir = os.path.join(TASK_DIR, "step1_scope_and_research", "references")

# WRONG — saves outside the task folder:
out_dir = os.path.join(os.path.dirname(__file__), "..", "figures", "stid_docs")  # NEVER DO THIS

Read the full file on GitHub · 2,529 lines

Changes

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.

  1. 5d ago Changed · +13 lines 53be14218f77
  2. 6d ago Changed · +102 lines 08040f1d63d1
  3. 9d ago Changed · +6 lines 967181e39c53
  4. 11d ago Changed · +6 lines 736a47e4a83c
  5. 12d ago Changed · +67 lines 7ac5c61fdd75
  6. 20d ago Changed · +10 lines · -59 tokens per session 072966cf98d8
  7. 27d ago First seen · 2,325 lines · 149 tokens per session scan A f8556b69e37f

Subscribe to this mod's changes

neqsim-task-workflow is a skill published in the GitHub repository equinor/neqsim (156 stars, last pushed today), licensed Apache-2.0. It adds 90 tokens to every session and 33,899 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-20.

Related

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens