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 drillinggit 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/drilling)<a href="https://agentmods.dev/skills/kucherenko/petropowers/drilling"><img src="https://agentmods.dev/badge/skills/kucherenko/petropowers/drilling.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.00027 | $0.01369 |
| Opus 5 | $0.00014 | $0.00685 |
| Sonnet 5 | $0.00005 | $0.00274 |
| Haiku 4.5 | $0.00003 | $0.00137 |
Grade A, and why
drilling 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Drilling Pipeline
Guide AI agents through well drilling operations and monitoring.
Purpose
Support drilling engineers in well planning, real-time monitoring, and post-well analysis.
Roles
- Drilling Engineer - Well design, casing program, drilling parameters
- Mud Engineer - Drilling fluids, hydraulics, wellbore stability
- Well Planner - Trajectory design, anti-collision, target intercept
- Rig Supervisor - Real-time operations, safety, equipment
Data Types
| Data | Source | Frequency |
|---|---|---|
| WOB, RPM, Torque | MWD/Surface | Real-time (1 Hz) |
| Mud weight, viscosity | Mud logging | Periodic |
| Flow rate, pit volume | Surface sensors | Real-time (1 Hz) |
| Gamma ray, resistivity | LWD | Real-time |
| Pressure | PWD (Pressure While Drilling) | Real-time |
| Trajectory | MWD | Every stand (~30 m) |
Workflow
Phase 1: Well Planning
- Define targets (from exploration)
- Design trajectory (3D wellpath)
- Design casing program (depths, sizes, grades)
- Select drilling fluids
- Identify hazards (pore pressure, fracture gradient, H2S)
- Optimize drilling parameters (ROP, hydraulics)
Phase 2: Real-Time Drilling
- Monitor drilling parameters
- Weight on Bit (WOB)
- RPM (Rotations Per Minute)
- Torque
- Rate of Penetration (ROP)
- Monitor mud returns
- Flow rate
- Mud weight
- Cuttings analysis
- Monitor LWD data
- Gamma ray
- Resistivity
- Pressure
- Detect anomalies
- Kicks (influx of formation fluid)
- Losses (mud lost to formation)
- Stuck pipe indicators
Phase 3: Post-Well Analysis
- Compare actual vs. planned
- Document lessons learned
- Update drilling database
- Optimize future wells
Key Parameters
| Parameter | Typical Range | Alert Threshold |
|---|---|---|
| WOB | 10-80 klbs | >120% of planned |
| Torque | 5-50 kft-lbs | >110% of planned |
| RPM | 60-180 rpm | Varies |
| ROP | 50-500 ft/hr | Depends on formation |
| Mud weight | 8-20 ppg | >0.5 ppg change |
| Flow in/out | 200-1000 gpm | Not equal = alert |
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 · 196 lines · 27 tokens per session scan A 869e0bb8f282
drilling is a skill published in the GitHub repository kucherenko/petropowers (11 stars, last pushed 5mo ago), licensed MIT. It adds 27 tokens to every session and 1,369 once invoked, about $0.0001 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 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…