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-community-skills --skill safety-function-coverage-screeninggit clone --depth 1 https://github.com/equinor/neqsim-community-skillsWrote 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-community-skills/safety-function-coverage-screening)<a href="https://agentmods.dev/skills/equinor/neqsim-community-skills/safety-function-coverage-screening"><img src="https://agentmods.dev/badge/skills/equinor/neqsim-community-skills/safety-function-coverage-screening/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-community-skills/safety-function-coverage-screening"><img src="https://agentmods.dev/badge/skills/equinor/neqsim-community-skills/safety-function-coverage-screening.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.00082 | $0.01109 |
| Opus 5 | $0.00041 | $0.00554 |
| Sonnet 5 | $0.00016 | $0.00222 |
| Haiku 4.5 | $0.00008 | $0.00111 |
Grade A, and why
neqsim-safety-function-coverage-screening 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Safety Function Coverage Screening
Use this skill for public, educational safety-function coverage screening. It checks whether a process component declares the protective functions that API RP 14C and ISO 10418 typically associate with that component type, reports the missing functions, and gives a coverage ratio so an agent can flag gaps before a formal Safety Analysis Function Evaluation (SAFE) chart review.
When to Use
- When a user asks whether a vessel or component has the usual API RP 14C protective functions.
- When an agent needs a quick protective-function gap check to scope a safety review.
- When examples must run without confidential SAFE charts, cause-and-effect matrices, or company safety specs.
Inputs
component_type: one ofpressure_vessel,separator,gas_pipeline_segment,liquid_pipeline_segment,fired_heater,compressor,pump, orwellhead.provided_functions: a collection of declared protective-function codes (for examplePSH,PSL,PSV,LSH,LSL,TSH,FSV,BSDV).
Outputs
component_type: the normalized component type.required_functions: the typically required protective-function codes for that type.provided_functions: the normalized declared functions.missing_functions: required functions that were not declared.coverage_ratio: fraction of required functions that are declared.coverage_warning:ok,watch, orgap.assumptions: public assumptions used by the placeholder model.
Engineering Method
The Python class SafetyFunctionCoverageModel uses the open API RP 14C / ISO 10418 concept only:
- each component type maps to a public set of typically required protective functions.
- the provided functions are compared to the required set to find missing functions.
- the coverage ratio is the count of provided required functions divided by the required count.
- the warning is a simple rule-based label that flags gaps for a formal review.
This is educational and screening-only logic. The required-function sets are simplified public defaults, not a project SAFE chart. It does not perform an undesirable-event analysis, evaluate detectable abnormal conditions, credit alternate protection, or assess independence and reliability. It is not a replacement for a formal API RP 14C / ISO 10418 SAFE-chart analysis and a qualified safety review.
What ships with it
6 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.
- examples/basic_safety_function_coverage_screening.py 871 B runs code
- pyproject.toml 566 B
- README.md 1.1 KB
- src/safety_function_coverage_screening/__init__.py 152 B runs code
- src/safety_function_coverage_screening/model.py 3.8 KB runs code
- tests/test_safety_function_coverage_model.py 1.3 KB runs code
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.
- 9d ago First seen · 101 lines · 82 tokens per session scan A a7c424a6065d
neqsim-safety-function-coverage-screening is a skill published in the GitHub repository equinor/neqsim-community-skills (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 82 tokens to every session and 1,109 once invoked, about $0.0004 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.
Other skills, from other repositories
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…