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 oil-gas-delegationgit 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/oil-gas-delegation)<a href="https://agentmods.dev/skills/kucherenko/petropowers/oil-gas-delegation"><img src="https://agentmods.dev/badge/skills/kucherenko/petropowers/oil-gas-delegation/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/oil-gas-delegation"><img src="https://agentmods.dev/badge/skills/kucherenko/petropowers/oil-gas-delegation.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.00024 | $0.00962 |
| Opus 5 | $0.00012 | $0.00481 |
| Sonnet 5 | $0.00005 | $0.00192 |
| Haiku 4.5 | $0.00002 | $0.00096 |
Grade A, and why
oil-gas-delegation 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 12d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Oil & Gas Delegation
Meta-skill that detects software tasks and routes them to appropriate petropowers skills.
Purpose
Oil & gas domain skills handle interpretation, analysis, and optimization recommendations. When a request requires building software (web apps, dashboards, APIs, databases), this skill delegates to petropowers skills.
Detection Logic
When a request contains any of these keywords, delegate to software development workflow:
- Web app, dashboard, visualization
- API, REST endpoint, GraphQL
- Database schema, data model, persistence
- Data pipeline, ETL, automation script
- Report generation system
- Alert notification system
Decision Flow
User request received
↓
Does request require building software?
↓
YES → Invoke oil-gas-delegation
↓
Route to appropriate petropowers workflow
↓
NO → Handle within domain skill
Delegation Workflows
Web Application / Dashboard
Request: "Build a drilling monitoring dashboard"
-
Invoke
petropowers:brainstormingskill- Refine dashboard requirements
- Identify data sources, users, features
- Create design document
-
Get user approval on design
-
Invoke
petropowers:writing-plansskill- Break into implementation tasks
- Define file structure, tech stack
-
Execute via
petropowers:subagent-driven-development- TDD for components
- Integration tests
- Code review between tasks
Data Pipeline
Request: "Create an automated LAS file processor"
- Invoke
petropowers:brainstorming - Get design approval
- Invoke
petropowers:writing-plans - Execute via
petropowers:subagent-driven-development
API Development
Request: "Build a REST API for production data"
- Invoke
petropowers:brainstorming - Get design approval
- Invoke
petropowers:writing-plans - Execute via
petropowers:subagent-driven-development
Quick Script
Request: "Write a script to convert SEG-Y to numpy"
- Check if truly needs TDD (one-off vs. production)
- If production: Use TDD workflow
- If one-off: Direct implementation with verification
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.
- 12d ago First seen · 151 lines · 24 tokens per session scan A 8fdffe4078a7
oil-gas-delegation is a skill published in the GitHub repository kucherenko/petropowers (11 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 962 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…