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 mtpygit 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/mtpy)<a href="https://agentmods.dev/skills/steadfastasart/geoscience-skills/mtpy"><img src="https://agentmods.dev/badge/skills/steadfastasart/geoscience-skills/mtpy/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/mtpy"><img src="https://agentmods.dev/badge/skills/steadfastasart/geoscience-skills/mtpy.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.01034 |
| Opus 5.5 | $0.00024 | $0.00414 |
| Sonnet 5.5 | $0.00012 | $0.00207 |
| Haiku 4.5 | $0.00006 | $0.00103 |
Grade A, and why
mtpy 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MTpy-v2: Transfer-Function Analysis
Install the mtpy-v2 distribution, which imports as mtpy. The older mtpy
distribution has a different API; do not install both in one environment.
The operations below were executed with MTpy-v2 2.1.4 and mt-metadata 1.0.10.
Read and establish conventions
from mtpy import MT
station = MT("station.edi")
station.read(get_elevation=False) # constructor alone does not load the file
frequency_hz = station.frequency
z = station.Z.z # complex tensor, shape (frequency, 2, 2)
sigma_z = station.Z.z_error # standard deviation, not EDI variance
rho = station.Z.resistivity # ohm m
phase = station.Z.phase # degrees, signed component phases
Confirm impedance units, time convention, axes, channel orientation, ZROT,
horizontal CRS and elevation reference from acquisition metadata. An EDI UNITS
field can describe distances rather than impedance. MT units are mV/km/nT;
the corresponding E/H impedance in ohms is multiplied by mu0 * 1000.
For MT units, apparent resistivity is 0.2 * abs(z)**2 / frequency_hz.
Do not call xy and yx TE/TM until a justified 2D strike coordinate system
has been established. A yx phase near -135 degrees can be valid under NED.
Read EDI conventions and missingness when handling empty values, variances or exports. mt-metadata can represent missing EDI values as zero, so inspect source masks before computing quality flags or rotating. Missing uncertainty is not an exact observation.
QC, rotation and export
Use the QC helper for direct-impedance EDI after confirming mV/km/nT, positive time convention and north/east/down:
python scripts/mt_analysis.py station.edi --output-dir results \
--impedance-units mt --sign-convention + --plot
Resolve the script relative to this skill directory. It exports every frequency and all four components with missingness, uncertainty and diagnostic flags, plus a JSON provenance file. It reopens its CSV and refuses existing output files. The default 50% relative-error threshold is a recorded diagnostic choice; choose task-specific criteria before examining the desired interpretation.
What ships with it
3 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.
- 1mo ago Changed · -117 lines · -60 tokens per session 23bcd9bf5c47
- 1mo ago Changed · +2 lines · +1 tokens per session 62602300b48d
- 2mo ago First seen · 209 lines · 119 tokens per session scan A 6998f460e9ef
mtpy is a skill published in the GitHub repository SteadfastAsArt/geoscience-skills (73 stars, last pushed 1mo ago), licensed MIT. It adds 60 tokens to every session and 1,034 once invoked, about $0.0002 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…