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 geolimegit 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/geolime)<a href="https://agentmods.dev/skills/steadfastasart/geoscience-skills/geolime"><img src="https://agentmods.dev/badge/skills/steadfastasart/geoscience-skills/geolime/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/geolime"><img src="https://agentmods.dev/badge/skills/steadfastasart/geoscience-skills/geolime.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.00053 | $0.00637 |
| Opus 5.5 | $0.00021 | $0.00255 |
| Sonnet 5.5 | $0.00011 | $0.00127 |
| Haiku 4.5 | $0.00005 | $0.00064 |
Grade A, and why
geolime 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GeoLime
Start by establishing which licensed distribution and version the project uses.
The public PyPI geolime==1.4.0 wheel contains a license-contact message and no
modelling API. pip install geolime alone does not establish an executable model
environment. This skill provides a preparation and review workflow; its licensed
modelling operations have not been executed in the repository's public tests.
Environment and API
Inspect project lock files, installed distribution metadata, local vendor docs and existing code before proposing imports. Use the vendor-provided environment or wheel only when the user already has access. Record its version and hash in the project; keep license files and credentials out of reports and source control. Do not invent class names from an unrelated release's examples.
If the functional package is unavailable, complete format/geometry QC and a reviewable model specification. State that execution remains unavailable. For an open-source implementation, assess GemPy or geostatistics tools against the actual required outputs; they are not drop-in GeoLime replacements.
Data and model contract
- Keep collar, survey and interval tables linked by stable drillhole identifiers. Verify from/to depths, overlaps, gaps, units and survey-angle conventions.
- Establish CRS, elevation datum, downhole versus vertical depth and survey desurveying method. Retain missing assays and detection limits distinctly.
- Record compositing, domain boundaries, density assumptions and block dimensions before estimating grades, volumes or tonnage. Point samples and block support are not interchangeable.
- Keep original assay values and transformation/back-transformation settings. Validate grade estimates with spatially separated drillholes and domain-aware residuals; random sample splits can leak adjacent intervals.
Validation and deliverables
Run the installed vendor's smallest documented example first, then validate a simple project-owned geometry with an independent volume calculation. Check block ordering and IDs in exports, domain coverage, mass/volume units and sensitivity to mesh/compositing choices. Label unrun code and unavailable methods explicitly.
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 · 60 lines · 53 tokens per session scan A 17592b409170
geolime is a skill published in the GitHub repository SteadfastAsArt/geoscience-skills (70 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 637 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…