agentmods.dev

neqsim-technology-assessment

neqsim-technology-assessment is a skill for Claude Code, Codex from equinor/neqsim-community-skills. It costs 87 tokens per session (2,226 once invoked), scanned A, original, Apache-2.0.

A technology assessment skill for judging how new and mature a technology is. It breaks the technology into parts, assigns novelty categories and a technology readiness level (TRL), and outlines likely qualification work.

In plain words
What is it for?
It helps assess equipment, systems, materials, processes, software, or services; identify benefits and risks; and prepare information for risk analysis and a formal report.
Why use it?
It helps a project decide which parts need further qualification before relying on a new technology or using a known technology in a new setting. It is an assessment, not design approval or a substitute for expert review.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 4repo today A scan 87 tokens original Apache-2.0

Good fit It helps assess equipment, systems, materials, processes, software, or services; identify benefits and risks; and prepare information for risk analysis and a formal report.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/equinor/neqsim-community-skills/neqsim-technology-assessment
View source ↗ equinor/neqsim-community-skills equinor.github.io
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-community-skills --skill neqsim-technology-assessment
Clone the repo
git clone --depth 1 https://github.com/equinor/neqsim-community-skills

Made for: Claude Code, Codex.

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-technology-assessment

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/equinor/neqsim-community-skills/neqsim-technology-assessment"><img src="https://agentmods.dev/badge/skills/equinor/neqsim-community-skills/neqsim-technology-assessment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 87 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,226 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.00087 $0.02226
Opus 5.5 $0.00035 $0.00890
Sonnet 5.5 $0.00017 $0.00445
Haiku 4.5 $0.00009 $0.00223

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

Security

Grade A, and why

neqsim-technology-assessment 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 10d ago.

The scan reads SKILL.md. This mod also ships 4 executable files (examples/basic_technology_assessment.py, src/technology_assessment/__init__.py, src/technology_assessment/model.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/field-development/neqsim-technology-assessment/SKILL.md · 193 lines

How it starts

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

Technology Assessment

Use this skill to structure the first stage of technology qualification for any technology a project may need (equipment, system, material, process, software, service or a known technology in a new application): the technology assessment. It answers which elements of a technology are new, how mature they are, how far they step outside existing experience, and what qualification effort is likely to be needed. The output is a technology_assessment.v1 mapping that feeds the failure-mode register (neqsim-technology-fmirr) and the report writer (neqsim-technology-assessment-report).

When to Use

  • A concept study introduces a technology, or an existing technology in a new application, and the project must know if qualification is needed.
  • A project study deliverable needs a maturity evaluation (novelty category and TRL) per system, sub-system and component.
  • Before running a failure-mode identification and risk-ranking workshop, to focus it on the novel elements.
  • Before writing a technology assessment report (see neqsim-technology-assessment-report).

Do not use it to qualify a technology, approve a design, or replace an expert panel. It structures judgement; it does not create evidence.

Inputs

  • technology: name of the technology.
  • qualification_basis: description, intended use, environment, functions, performance expectations, applicable regulatory requirements. Start with the design-basis elements of the project and refine as technologies are selected.
  • role: critical_to_business_case and qualified_fallback_available.
  • elements: the decomposition. Each has id, name, optional parent_id, function, kind (system, subsystem, component, function, interface, software, process), technology_novelty (proven, limited_history, new), application_area (known, limited_knowledge, new), qualified_by (none, company, others), trl (0-7), evidence, lifecycle_phases.
  • step_out: items per dimension (design, manufacturing, installation, operability, fluids, operating_conditions, lifetime) with the experience basis, the proposed value and optionally numeric reference_value / proposed_value and a direction (max or min). Set experience_documented: false when no documented experience exists for the dimension; it is then reported as a data gap, not as an assessed dimension.
  • benefits, risks (with optional mitigation), standardisation, multi_implementation.
  • interfaces_untested, optional system_trl_override with a rationale.

Read the full file on GitHub · 193 lines

Files

What ships with it

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

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. 10d ago First seen · 193 lines · 87 tokens per session scan A 6c1440b47feb

Subscribe to this mod's changes

neqsim-technology-assessment is a skill published in the GitHub repository equinor/neqsim-community-skills (4 stars, last pushed today), licensed Apache-2.0. It adds 87 tokens to every session and 2,226 once invoked, about $0.0003 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-28.

PlanningScientific
Related

neqsim-technology-assessment compared with skills from other repositories

neqsim-technology-assessment next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
neqsim-technology-assessmentequinor/neqsim-community-skillsSkill4todayApache-2.0A87Claude Code, Codex
instrument-data-to-allotropeanthropics/knowledge-work-pluginsSkill35k3d agoApache-2.0A123Claude Code
exploratory-data-analysisK-Dense-AI/scientific-agent-skillsSkill56k4d agoMITA83Claude Code
matlabK-Dense-AI/scientific-agent-skillsSkill56k4d agoMITA44Claude Code
phylogeneticsK-Dense-AI/scientific-agent-skillsSkill56k4d agoMITA71Claude Code, Codex
research-engineerdavila7/claude-code-templatesSkill33kyesterdayMITA43Claude Code, Codex
mapping-to-snomedmaziyarpanahi/openmedSkill5.8kyesterdayApache-2.0A205Claude Code