standards-traceability-curator

standards-traceability-curator is an agent for coding agents from equinor/neqsim. It costs 29 tokens per session (337 once invoked), scanned A, original, Apache-2.0.

A review process for linking claims about technical standards to specific standards, revisions, clauses, and supporting evidence. Standards are formal documents that define technical requirements or recommended practices.

In plain words
What is it for?
Use it to build a standards traceability matrix, extract requirements, and identify unsupported compliance wording.
Why use it?
It helps reveal when a compliance or standards claim is too strong for the available evidence. It also keeps standards references traceable during review.

Agent

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.

agentmods
npx agentmods add agents/equinor/neqsim/standards_traceability_curator.paperlab
Clone the repo
git clone --depth 1 https://github.com/equinor/neqsim

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 standards-traceability-curator

README.md
[![agentmods](https://agentmods.dev/badge/agents/equinor/neqsim/standards_traceability_curator.paperlab.svg)](https://agentmods.dev/agents/equinor/neqsim/standards_traceability_curator.paperlab)
Your own site
<a href="https://agentmods.dev/agents/equinor/neqsim/standards_traceability_curator.paperlab"><img src="https://agentmods.dev/badge/agents/equinor/neqsim/standards_traceability_curator.paperlab.svg" alt="Measured on agentmods" height="20"></a>
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 337 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00029 $0.00337
Opus 5 $0.00015 $0.00169
Sonnet 5 $0.00006 $0.00067
Haiku 4.5 $0.00003 $0.00034

Measured 2d ago against content hash 916bd57798d0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

standards-traceability-curator 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.

neqsim-paperlab/agents/standards_traceability_curator.paperlab.md · 54 lines

What it actually says

Standards Traceability Curator Agent

You make standards references defensible without overstating compliance.

Loaded Skills

  • paperlab_standards_clause_traceability
  • neqsim_standard_requirement_extraction
  • paperlab_scientific_traceability_audit

Required Context

Read these files before analysis when they exist:

  • standards-heavy chapter markdown files
  • standards_map.json
  • source manifests
  • public standards notes or extracted requirement tables

Workflow

  1. Extract references to API, DNV, ISO, IEC, ASME, NORSOK, local regulations, and company technical requirements.
  2. Classify statements as broad reference, design requirement, compliance claim, calculation method, or contextual guidance.
  3. Map high-value statements to standard, revision, clause or paraphrased requirement, evidence source, and confidence.
  4. Flag unsupported compliance language and recommend softer wording when only broad evidence exists.
  5. Maintain a standards traceability matrix for release review.

Output

  • standards_traceability_matrix.json
  • unsupported_compliance_language.md
  • suggested wording changes for broad or unsupported standards claims

Guardrails

  • Never invent clause numbers or quote restricted standards text.
  • Use paraphrased requirements unless the source permits direct quotation.
  • Distinguish educational guidance from formal compliance documentation.
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. 2d ago First seen · 54 lines · 29 tokens per session scan A 916bd57798d0

Subscribe to this mod's changes

standards-traceability-curator is an agent published in the GitHub repository equinor/neqsim (150 stars, last pushed today), licensed Apache-2.0. It adds 29 tokens to every session and 337 once invoked, about $0.0001 per session on Opus 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-03.

Related

Other agents, from other repositories

compliance_agent

Runs PRISMA-trAIce + RAISE compliance checks at Stage 2.5 / 4.5 integrity gates and emits Schema 12 compliancereport.

Imbad0202/academic-research-skills · 37 tokens

compliance_agent

Runs PRISMA-trAIce + RAISE compliance checks at Stage 2.5 / 4.5 integrity gates and emits Schema 12 compliancereport.

Imbad0202/academic-research-skills-codex · 37 tokens

biomaterials-scientist

Reasons from material-biology interfaces, degradation-product toxicity, and mechanical mismatch to host tissue through ISO 10993 biological evaluation plans, ISO 10993-12 extract conditions, GPC/ICP/SEM characterization, and sterilization validation while treating endotoxin contamination, pH shift from acidic…

K-Dense-AI/scientific-agents · 84 tokens

biomedical-engineer

Reasons from ISO 14971 risk management, ISO 10993 biocompatibility matrices, ASTM F/ISO 14242 mechanical and wear testing, and FDA 510(k) substantial equivalence; treats stress shielding, UHMWPE osteolysis, F2129 corrosion artifacts, and predicate/material mismatches as first-class failure modes.

K-Dense-AI/scientific-agents · 74 tokens

gxp-validator

Computer Systems Validation and compliance lifecycle specialist covering 21 CFR Part 11, EU Annex 11, GAMP 5, compliance architecture, change control, electronic signatures, SOPs, data integrity monitoring, training programmes, and system decommissioning.

pjt222/agent-almanac · 53 tokens

Medical Device Systems Engineer

Principal medical device SE specializing in IEC 62304 software lifecycle, ISO 14971 risk management, FDA design controls and QMSR, EU MDR technical documentation, and multi-tool MBSE crosswalks for Class II/III and SaMD programs.

ajhcs/mbse-agents · 56 tokens