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 kucherenko/petropowers --skill well-log-analysisgit clone --depth 1 https://github.com/kucherenko/petropowersWrote 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/kucherenko/petropowers/well-log-analysis)<a href="https://agentmods.dev/skills/kucherenko/petropowers/well-log-analysis"><img src="https://agentmods.dev/badge/skills/kucherenko/petropowers/well-log-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.
<a href="https://agentmods.dev/skills/kucherenko/petropowers/well-log-analysis"><img src="https://agentmods.dev/badge/skills/kucherenko/petropowers/well-log-analysis.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.00021 | $0.03374 |
| Opus 5 | $0.00010 | $0.01687 |
| Sonnet 5 | $0.00004 | $0.00675 |
| Haiku 4.5 | $0.00002 | $0.00337 |
Grade B, and why
well-log-analysis scanned grade B with 2 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 9d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
storage_resp = requests.post( "https://api.osdu.com/api/dataset/v1/storageInstructions", Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
storage_resp = requests.post( How it starts
The opening of the file, as written. The whole thing — 489 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Well Log Analysis
Read, analyze, and manipulate well log data in LAS format using lasio library.
Purpose
Handle well log operations across all oil & gas pipeline skills. Provides code patterns for reading LAS files, extracting metadata, performing petrophysical calculations, and exporting data.
Reference Materials
Primary source: lasio documentation
Library: lasio
Related packages:
Dependencies
pip install lasio pandas matplotlib numpy
Capabilities
1. Read LAS Files
import lasio
# Read LAS file
log = lasio.read('well_log.las')
# Access well metadata
print(f"Well: {log.well['WELL'].value}")
print(f"Field: {log.well['FLD'].value if 'FLD' in log.well else 'N/A'}")
print(f"Company: {log.well['COMP'].value if 'COMP' in log.well else 'N/A'}")
# Access curve data
print(f"Curves: {[curve.mnemonic for curve in log.curves]}")
print(f"Depth range: {log.index_min} to {log.index_max} {log.index_unit}")
2. Export to DataFrame
import lasio
import pandas as pd
log = lasio.read('well_log.las')
# Convert to pandas DataFrame
df = log.df()
# Access specific curves
depth = df.index
gamma_ray = df['GR']
density = df['RHOB']
neutron = df['NPHI']
print(df.head())
3. Access Header Metadata
import lasio
log = lasio.read('well_log.las')
# Version section
print(f"Version: {log.version['VERS'].value}")
print(f"Wrap: {log.version['WRAP'].value}")
# Well section
print(log.well)
# Parameters section
print(log.params)
# Other section
for item in log.other:
print(item)
# Curves section
for curve in log.curves:
print(f"{curve.mnemonic}: {curve.unit} - {curve.descr}")
4. Petrophysical Calculations
import lasio
import numpy as np
log = lasio.read('well_log.las')
df = log.df()
# Calculate porosity from density
# Phi = (matrix - bulk) / (matrix - fluid)
matrix_density = 2.65 # g/cc (sandstone)
fluid_density = 1.0 # g/cc (water)
bulk_density = df['RHOB'].values
porosity = (matrix_density - bulk_density) / (matrix_density - fluid_density)
porosity = np.clip(porosity, 0, 0.5) # Clamp to reasonable range
print(f"Average porosity: {porosity.mean():.2%}")
# Calculate water saturation (Archie equation)
# Sw = ((a * Rw) / (Phi^m * Rt))^(1/n)
a = 1.0
m = 2.0
n = 2.0
Rw = 0.1 # ohm-m (formation water resistivity)
phi = porosity
Rt = df['RT'].values # true resistivity
Sw = ((a * Rw) / (phi**m * Rt))**(1/n)
Sw = np.clip(Sw, 0, 1)
print(f"Average water saturation: {Sw.mean():.2%}")
# Calculate shale volume from gamma ray
GR = df['GR'].values
GR_min = GR.min()
GR_max = GR.max()
Vsh = (GR - GR_min) / (GR_max - GR_min)
Vsh = np.clip(Vsh, 0, 1)
print(f"Average shale volume: {Vsh.mean():.2%}")
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.
- 9d ago First seen · 489 lines · 21 tokens per session scan B 0a352fd35c8d
well-log-analysis is a skill published in the GitHub repository kucherenko/petropowers (11 stars, last pushed 5mo ago), licensed MIT. It adds 21 tokens to every session and 3,374 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
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
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for 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…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…