agentmods.dev

well-analysis

well-analysis is a command for Claude Code from SteadfastAsArt/geoscience-skills. It costs 16 tokens per session (501 once invoked), scanned A, original, MIT.

A guided workflow for analyzing well logs, which are measurements recorded along a drilled well. It covers loading data, studying rock and fluid properties, identifying rock layers, and making plots.

In plain words
What is it for?
Loading LAS or DLIS files, checking curves and depth data, performing petrophysics, identifying lithology and stratigraphy, and creating 2D or 3D visualizations.
Why use it?
It helps choose the right processing path based on the file format, analysis goal, and visualization needed.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

not rated 77repo +3 4d ago A scan 16 tokens original MIT

Good fit Loading LAS or DLIS files, checking curves and depth data, performing petrophysics, identifying lithology and stratigraphy, and creating 2D or 3D visualizations.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/steadfastasart/geoscience-skills/well-analysis
View source ↗ SteadfastAsArt/geoscience-skills
Install

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.

Clone the repo
git clone --depth 1 https://github.com/SteadfastAsArt/geoscience-skills

Made for: Claude Code.

Wrote 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.

agentmods badge for well-analysis

README.md
[![agentmods](https://agentmods.dev/badge/commands/steadfastasart/geoscience-skills/well-analysis/github.svg)](https://agentmods.dev/commands/steadfastasart/geoscience-skills/well-analysis)
Your own site
<a href="https://agentmods.dev/commands/steadfastasart/geoscience-skills/well-analysis"><img src="https://agentmods.dev/badge/commands/steadfastasart/geoscience-skills/well-analysis/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.

agentmods 80×15 button for well-analysis

Your own site · 80×15
<a href="https://agentmods.dev/commands/steadfastasart/geoscience-skills/well-analysis"><img src="https://agentmods.dev/badge/commands/steadfastasart/geoscience-skills/well-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 501 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00016 $0.00501
Opus 5.5 $0.00006 $0.00200
Sonnet 5.5 $0.00003 $0.00100
Haiku 4.5 $0.00002 $0.00050

Measured 2mo ago against content hash 7373b48462f2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

well-analysis 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 2mo 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.

.claude/commands/well-analysis.md · 63 lines

What it actually says

Well Log Analysis Workflow

Guide the user through a well log analysis pipeline. Determine the appropriate skill chain based on their data format and analysis goals.

Decision Tree

  1. What format is the well data?

    • LAS (.las) → Use lasio skill for loading
    • DLIS (.dlis) → Use dlisio skill for loading
    • CSV / already loaded → Skip to processing with welly

  2. What analysis is needed?

    • Multi-well management, curve QC → Use welly skill
    • Petrophysics (porosity, saturation, cutoffs) → Use petropy skill
    • Lithology / stratigraphy intervals → Use striplog skill

  3. Visualization needs?

    • Log plots, cross-plots → matplotlib via welly
    • 3D wellbore trajectories → Use pyvista skill

Skill Chain

lasio/dlisio (load) → welly (manage/QC) → petropy (petrophysics) → striplog (lithology)
                                                                  ↘ pyvista (3D viz)

Step Prompts

For each step, invoke the relevant domain skill and follow its guidance.

Step 1: Data Loading

  • Load well log files and inspect available curves
  • Check header metadata (well name, depth units, null values)
  • Validate depth range and sampling interval

Step 2: Quality Control

  • Identify missing or null values in key curves
  • Check curve mnemonics and units consistency
  • Merge or splice curves from multiple runs if needed

Step 3: Petrophysics

  • Compute shale volume (Vsh) from GR or SP
  • Calculate porosity (density, neutron, sonic methods)
  • Estimate water saturation (Archie or dual-water)
  • Apply net pay cutoffs

Step 4: Lithology Classification

  • Define lithology intervals from log response
  • Build striplog from interpreted zones
  • Correlate across multiple wells

Step 5: Visualization

  • Log plots with tracks (GR, resistivity, porosity, saturation)
  • Cross-plots for mineral identification
  • 3D wellbore rendering with property logs

$ARGUMENTS

Changes

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.

  1. 2mo ago First seen · 63 lines · 16 tokens per session scan A 7373b48462f2

Subscribe to this mod's changes

well-analysis is a command published in the GitHub repository SteadfastAsArt/geoscience-skills (77 stars, last pushed 4d ago), licensed MIT. It adds 16 tokens to every session and 501 once invoked, about $0.0001 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.

Claude CodeScientificai-agentsgeophysicsgeosciencegeostatisticsnetCDF
Related

well-analysis compared with commands from other repositories

well-analysis next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
well-analysisSteadfastAsArt/geoscience-skillsCommand774d agoMITA16Claude Code
plotzhouziyue233/great-econometricsCommand86mo agononeA44Claude Code
graphite-morphology-classifyDaxxSec/cognitropy-labCommand14mo agononeA0Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code