Borrowing it
Nothing to install: this file belongs to SteadfastAsArt/geoscience-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/SteadfastAsArt/geoscience-skills/main/CLAUDE.mdgit 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/instructions/steadfastasart/geoscience-skills/claude-md)<a href="https://agentmods.dev/instructions/steadfastasart/geoscience-skills/claude-md"><img src="https://agentmods.dev/badge/instructions/steadfastasart/geoscience-skills/claude-md.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.01643 | $0.01643 |
| Opus 5 | $0.00822 | $0.00822 |
| Sonnet 5 | $0.00329 | $0.00329 |
| Haiku 4.5 | $0.00164 | $0.00164 |
Grade A, and why
geoscience-skills CLAUDE.md 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 8d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
Geoscience Skills Library - A comprehensive open-source library of 30 geoscience skills for AI coding assistants. Each skill provides expert-level guidance for Python geoscience libraries, covering seismic processing, well log analysis, geological modelling, geophysical inversion, geostatistics, and more.
Mission: Enable AI coding agents to assist geoscientists with domain-specific Python workflows, from data loading to interpretation and visualization.
Repository Architecture
Directory Structure (30 Skills Across 17 Domains)
Skills are organized by Python library name in a flat directory structure:
- Seismic & Seismology:
obspy/,segyio/,disba/ - Well Log Analysis:
lasio/,welly/,dlisio/,striplog/,petropy/ - 3D Geological Modelling:
gempy/,loopstructural/,gemgis/ - Geophysical Inversion:
simpeg/,devito/,pylops/,pygimli/ - Potential Fields:
harmonica/ - Rock Physics:
bruges/ - Geostatistics & Spatial:
verde/,geostatspy/,scikit-gstat/,gnnwr/ - Hydrology:
pastas/ - Surface Processes:
landlab/ - Structural Geology:
mplstereonet/ - Geochemistry:
pyrolite/ - Near-Surface Geophysics:
gprpy/,mtpy/ - Data Formats:
xarray/ - Visualization:
pyvista/ - Utilities:
pooch/
Skill File Structure
Each skill follows a standardized format:
skill-name/
├── SKILL.md # Main guidance (200-300 lines with YAML frontmatter)
├── references/ # Deep documentation (one level deep)
│ ├── topic1.md # Specific reference topic
│ └── topic2.md # Another reference topic
└── scripts/ # Helper scripts (optional)
└── example.py # Utility script
Workflow and Agent Architecture
The library includes additional infrastructure beyond domain skills:
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.
- 8d ago First seen · 168 lines · 1,643 tokens per session scan A 8b3884817692
geoscience-skills CLAUDE.md is an instructions file published in the GitHub repository SteadfastAsArt/geoscience-skills (57 stars, last pushed 5mo ago), licensed MIT. It adds 1,643 tokens to every session, about $0.0082 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.