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 boulegit 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/boule)<a href="https://agentmods.dev/skills/steadfastasart/geoscience-skills/boule"><img src="https://agentmods.dev/badge/skills/steadfastasart/geoscience-skills/boule/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/boule"><img src="https://agentmods.dev/badge/skills/steadfastasart/geoscience-skills/boule.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.00051 | $0.00663 |
| Opus 5.5 | $0.00020 | $0.00265 |
| Sonnet 5.5 | $0.00010 | $0.00133 |
| Haiku 4.5 | $0.00005 | $0.00066 |
Grade A, and why
boule 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Boule
Use the ellipsoid and coordinate convention attached to the actual observations. An ellipsoid is a reference surface; choosing WGS84 does not transform coordinates from another datum or reference epoch.
Inputs and conventions
For the 0.6 API, coordinates are a tuple (longitude, latitude, height) for
geodetic input: angles in degrees, ellipsoidal height in metres. Spherical input
uses geocentric latitude and radius in metres, not elevation. Orthometric height
above a geoid requires a separate geoid model before use as ellipsoidal height.
Choose an existing ellipsoid such as WGS84 or GRS80 from source metadata, or
define a documented body with consistent parameters. Do not infer the ellipsoid
from a column merely called height.
Gravity and coordinate conversion
# example: ellipsoid-gravity
import numpy as np
import boule
longitude_deg = np.array([0.0, 10.0, 0.0])
latitude_deg = np.array([0.0, 45.0, 90.0])
height_m = np.zeros(3)
geodetic = (longitude_deg, latitude_deg, height_m)
gravity_mgal = boule.WGS84.normal_gravity(geodetic)
gravity_si = boule.WGS84.normal_gravity(geodetic, si_units=True)
spherical = boule.WGS84.geodetic_to_spherical(geodetic)
roundtrip = boule.WGS84.spherical_to_geodetic(spherical)
Default gravity is mGal: 1 mGal = 10⁻⁵ m/s². At zero height, reference gravity is about 9.7803253 m/s² at the equator and 9.8321849 m/s² at the poles. Mid-latitude geocentric latitude differs from geodetic latitude. Check both units and limits.
Applying corrections
Specify whether the requested quantity is observed gravity, normal gravity, disturbance or anomaly, with its height and sign convention. Subtraction of normal gravity alone is not a Bouguer, terrain or tide correction. Preserve instrument units and datum/epoch provenance through any handoff to a potential-field model.
Read the normal gravity guide and API for the selected body.
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 First seen · 62 lines · 51 tokens per session scan A 553fe1229ff2
boule is a skill published in the GitHub repository SteadfastAsArt/geoscience-skills (70 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 663 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-09-16.
Other skills, from other repositories
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.
obspy-seismology
Seismological data analysis with ObsPy — FDSN waveform download, response removal, phase picking, moment tensor inversion, and seismicity mapping.
xarray-netcdf
Labeled multi-dimensional array analysis with xarray: NetCDF/HDF5 I/O, lazy Dask loading, rechunking, Zarr stores, and CF conventions.
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…
exploratory-data-analysis
Performs bounded, local exploratory analysis of explicitly supported scientific files. Supports 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…