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 bathymetry-profile-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/bathymetry-profile-screening)<a href="https://agentmods.dev/skills/equinor/neqsim-community-skills/bathymetry-profile-screening"><img src="https://agentmods.dev/badge/skills/equinor/neqsim-community-skills/bathymetry-profile-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/bathymetry-profile-screening"><img src="https://agentmods.dev/badge/skills/equinor/neqsim-community-skills/bathymetry-profile-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.00060 | $0.01403 |
| Opus 5 | $0.00030 | $0.00701 |
| Sonnet 5 | $0.00012 | $0.00281 |
| Haiku 4.5 | $0.00006 | $0.00140 |
Grade A, and why
neqsim-bathymetry-profile-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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bathymetry Profile Screening
Use this skill for a quick, public screening of a seabed bathymetry profile along a route. Given a set of sounding points (distance along route and water depth), it sorts and linearly interpolates depth at requested distances, computes seabed slopes between soundings, and flags candidate steep sections. It is intentionally simple and should guide users toward validated free-span, on-bottom-stability, and NeqSim hydraulic workflows.
When to Use
- When a user supplies seabed soundings along a route and wants an interpolated depth profile.
- When an engineer needs slope screening and candidate steep-section flags for early planning.
- When an agent should explain that validated span and stability analyses are required for design-grade work.
Inputs
soundings: a list of seabed points, each withdistance_m(along route) anddepth_m(water depth, positive downwards).query_distances: optional list of distances at which to interpolate depth.max_slope_deg: configurable public seabed-slope guideline (constructor, default 10 degrees).
Outputs
sorted_soundings: the soundings sorted by distance.interpolated: depth at each requested query distance (linear interpolation).slopes: per-interval seabed slope between consecutive soundings.steep_sections: intervals whose slope is at or above the guideline.max_slope_deg: the steepest interval slope.min_depth_mandmax_depth_m: shallowest and deepest soundings.slope_warning:ok,watch, orhighagainst the public slope guideline.neqsim_available: whether the optional NeqSim package is importable.assumptions: public assumptions and required follow-up.
Engineering Method
Soundings are sorted by along-route distance. Depth at a query distance is found by linear interpolation between the two bracketing soundings; query distances outside the sounding range are clamped to the nearest end and flagged. The slope of each interval is atan2(|depth_change|, distance_change) in degrees. Any interval at or above the max_slope_deg guideline is reported as a candidate steep section. The slope warning compares the steepest interval to the guideline: at or above is high, above 80 % is watch, otherwise ok.
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.
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 · 114 lines · 60 tokens per session scan A 4ea5b9eb0276
neqsim-bathymetry-profile-screening is a skill published in the GitHub repository equinor/neqsim-community-skills (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 60 tokens to every session and 1,403 once invoked, about $0.0003 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…