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 SteadfastAsArt/geoscience-skills --skill seismic-interpretationgit clone --depth 1 https://github.com/SteadfastAsArt/geoscience-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/steadfastasart/geoscience-skills/seismic-interpretation)<a href="https://agentmods.dev/skills/steadfastasart/geoscience-skills/seismic-interpretation"><img src="https://agentmods.dev/badge/skills/steadfastasart/geoscience-skills/seismic-interpretation/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/steadfastasart/geoscience-skills/seismic-interpretation"><img src="https://agentmods.dev/badge/skills/steadfastasart/geoscience-skills/seismic-interpretation.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.00037 | $0.03629 |
| Opus 5.5 | $0.00015 | $0.01452 |
| Sonnet 5.5 | $0.00007 | $0.00726 |
| Haiku 4.5 | $0.00004 | $0.00363 |
Grade A, and why
seismic-interpretation 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 1mo 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 — 296 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Seismic Interpretation Workflow
End-to-end pipeline for seismic data analysis, from loading SEG-Y files through signal processing, rock physics modelling, and 3D visualization.
Skill Chain
segyio obspy bruges disba pyvista
[SEG-Y I/O] --> [Signal Proc] --> [Rock Physics] --> [Dispersion] --> [3D Viz]
| | | | |
Load traces Filter/FFT AVO modelling Surface waves Volume render
Read headers Instrument resp Fluid sub Phase velocity Slice display
3D geometry Spectral anal Synthetics Inversion Horizon pick
Decision Points
| Question | If Yes | If No |
|---|---|---|
| Working with SEG-Y files? | Start with segyio |
Use obspy for miniSEED/SAC |
| Need frequency filtering or spectral analysis? | Use obspy signal tools |
Skip to rock physics |
| Performing AVO or fluid substitution? | Use bruges |
Skip to visualization |
| Analysing surface waves (MASW/SASW)? | Use disba for dispersion |
Skip disba |
| Need 3D volume rendering? | Use pyvista |
Use matplotlib for 2D |
Step-by-Step Orchestration
Stage 1: Data Loading (segyio)
This loader handles a complete post-stack grid, including crossline-fast trace ordering. Supply the survey's projected CRS from authoritative metadata. Header coordinate units must be length units, and the binary measurement system must identify metres or feet. Angular coordinates need reprojection first. Confirm that the sample axis represents two-way time in milliseconds for this workflow.
import segyio
import numpy as np
def load_poststack(path, crs):
if not isinstance(crs, str) or not crs.strip():
raise ValueError('Supply the projected survey CRS; SEG-Y coordinates alone do not identify it')
with segyio.open(path, 'r', iline=189, xline=193) as f:
if len(f.offsets) != 1:
raise ValueError('Select or stack offsets before loading a post-stack cube')
time_ms = np.asarray(f.samples, dtype=float).copy()
if len(time_ms) < 2 or not np.all(np.isfinite(time_ms)):
raise ValueError('Require at least two finite time samples')
dt_ms = time_ms[1] - time_ms[0]
if dt_ms <= 0 or not np.allclose(np.diff(time_ms), dt_ms):
raise ValueError('Resample inconsistent time sampling before building a cube')
to_metres = {1: 1.0, 2: 0.3048}.get(f.bin[segyio.BinField.MeasurementSystem])
if to_metres is None:
raise ValueError('Confirm SEG-Y measurement system: metres or feet')
ilines, xlines = np.array(f.ilines), np.array(f.xlines)
ii = {int(value): index for index, value in enumerate(ilines)}
jj = {int(value): index for index, value in enumerate(xlines)}
shape = (len(ilines), len(xlines))
cube = np.empty((*shape, len(time_ms)), dtype=np.float32)
easting, northing = np.empty(shape), np.empty(shape)
seen = np.zeros(shape, dtype=bool)
for trace_index, header in enumerate(f.header):
i, j = ii[header[189]], jj[header[193]]
if seen[i, j]:
raise ValueError('Duplicate inline/crossline location')
if header[segyio.TraceField.CoordinateUnits] != 1:
raise ValueError('Require projected coordinates in length units')
if (not np.isclose(header[segyio.TraceField.TRACE_SAMPLE_INTERVAL] / 1000, dt_ms)
or not np.isclose(header[segyio.TraceField.DelayRecordingTime], time_ms[0])):
raise ValueError('Trace time axes differ; align them before stacking into a cube')
scalar = header[segyio.TraceField.SourceGroupScalar]
factor = scalar if scalar > 0 else 1 / abs(scalar) if scalar < 0 else 1.0
easting[i, j] = header[segyio.TraceField.CDP_X] * factor * to_metres
northing[i, j] = header[segyio.TraceField.CDP_Y] * factor * to_metres
cube[i, j] = f.trace[trace_index]
seen[i, j] = True
if not np.all(seen):
raise ValueError('Incomplete grid: retain missing traces explicitly or regrid')
return dict(amplitude=cube, easting_m=easting, northing_m=northing,
time_ms=time_ms, crs=crs, ilines=ilines, xlines=xlines)
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.
- 1mo ago Changed · +78 lines 180b528488c7
- 2mo ago First seen · 218 lines · 37 tokens per session scan A 585c9a3d1e0a
seismic-interpretation is a skill published in the GitHub repository SteadfastAsArt/geoscience-skills (73 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 3,629 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
earthquake-guide
Gates and workflows for the earthquake tools (USGS ComCat and EMSC). Use to judge how bad a quake was, read USGS aftershock odds, check whether a depth or location holds up, match one event across USGS and EMSC, or count and list events over years or in a region — before concluding from a missing product, a default…
glm-lake-mendota
Simulate vertical water temperature profiles for lakes using the General Lake Model (GLM), calibrate key parameters to minimize RMSE against field observations, and produce validated NetCDF output.
xarray-netcdf
Labeled multi-dimensional array analysis with xarray: NetCDF/HDF5 I/O, lazy Dask loading, rechunking, Zarr stores, and CF conventions.
obspy-seismology
Seismological data analysis with ObsPy — FDSN waveform download, response removal, phase picking, moment tensor inversion, and seismicity mapping.
soil-data
Soil data analysis via SoilGrids 2.0 REST API and SSURGO: SOC stocks, texture classification, kriging interpolation, and soil profile visualization.
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…