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.svg" alt="Measured on agentmods" 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.00119 | $0.01609 |
| Opus 5 | $0.00060 | $0.00805 |
| Sonnet 5 | $0.00024 | $0.00322 |
| Haiku 4.5 | $0.00012 | $0.00161 |
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 7d 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mtpy - Magnetotelluric Analysis
Quick Reference
from mtpy import MT, MTCollection
# Read single station
mt = MT('station001.edi')
# Access data
Z = mt.Z # Complex impedance tensor
freq = mt.frequency # Frequency array
rho_xy = mt.apparent_resistivity[:, 0, 1] # Apparent resistivity
# Station info
print(mt.station, mt.latitude, mt.longitude)
# Write EDI
mt.write_edi('output.edi')
Key Classes
| Class | Purpose |
|---|---|
MT |
Single station MT data container |
MTCollection |
Multiple stations management |
PlotMTResponse |
Plot impedance, resistivity, phase |
PlotPhaseTensor |
Phase tensor ellipse visualization |
PlotPseudoSection |
Profile pseudosection display |
PlotStrike |
Strike direction analysis |
Essential Operations
Load and Inspect EDI
from mtpy import MT
mt = MT('station001.edi')
print(f"Station: {mt.station}")
print(f"Location: ({mt.latitude}, {mt.longitude})")
print(f"Frequencies: {len(mt.frequency)} points")
print(f"Period range: {1/mt.frequency.max():.2f} - {1/mt.frequency.min():.0f} s")
Load Multiple Stations
from mtpy import MTCollection
mc = MTCollection()
mc.from_edis('survey_data/*.edi')
print(f"Loaded {len(mc)} stations")
for station in mc:
print(f" {station.station}: ({station.latitude:.4f}, {station.longitude:.4f})")
Plot MT Response
from mtpy import MT
from mtpy.imaging import PlotMTResponse
mt = MT('station001.edi')
plot = PlotMTResponse(mt)
plot.plot() # Apparent resistivity and phase
Phase Tensor Analysis
from mtpy import MT
from mtpy.imaging import PlotPhaseTensor
mt = MT('station001.edi')
# Get phase tensor parameters
phi_min = mt.phase_tensor.phimin
phi_max = mt.phase_tensor.phimax
skew = mt.phase_tensor.skew # 3D indicator
# Plot
pt = PlotPhaseTensor(mt)
pt.plot()
Rotate Impedance Tensor
from mtpy import MT
mt = MT('station001.edi')
mt_rotated = mt.rotate(30) # 30 degrees clockwise
mt.rotate_to_strike() # Auto-rotate to geoelectric strike
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.
- 7d ago First seen · 209 lines · 119 tokens per session scan A 6998f460e9ef
mtpy is a skill published in the GitHub repository SteadfastAsArt/geoscience-skills (57 stars, last pushed 5mo ago), licensed MIT. It adds 119 tokens to every session and 1,609 once invoked, about $0.0006 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-08-30.
Other skills, from other repositories
mxl-driver-dftbplus
This skill should be used when users want to couple MaxwellLink to the MaxwellLink-aware DFTB+ fork via the MaxwellLinkSocket block, including real-time Ehrenfest dynamics, VelocityVerlet Born-Oppenheimer MD, dipole-derivative choices, build/install, and TCP/UNIX socket connection patterns.
mxl-multimode
This skill should be used when users need the MaxwellLink multimode Fabry-Pérot cavity solver to study a spatial grid of molecules coupled to many photonic modes (mesoscale VSC), in either socket or embedded mode.
paper_tutorial_plasmon_heating
Dual-purpose tutorial to reproduce manuscript Figure 5b, 5d, and 5e plasmonic flux and HCN heating maps (EM-only, TLS, and ASE/BOMD), and to transfer the workflow to related plasmon-molecule systems by adjusting geometry, molecular model, and run procedures.
paper_tutorial_vsc_water
Dual-purpose tutorial to reproduce manuscript liquid-water vibrational strong-coupling spectra and CPU scaling (single-mode cavity plus Meep Bragg resonator), and to adapt the same procedure to related VSC systems by retuning cavity/resonator parameters, size ladders, and execution settings.
mxl-meep
This skill should be used when users need MaxwellLink + Meep FDTD workflows, including embedded vs socket coupling, MPI considerations, and recommended templates.
mxl-core
This skill should be used when users need the canonical MaxwellLink workflow, including socket vs embedded coupling, units/time handling, and MPI/HPC invariants.