Borrowing it
Nothing to install: this file belongs to ameyxd/petromcp. 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/ameyxd/petromcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/ameyxd/petromcpWrote 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/ameyxd/petromcp/claude-md)<a href="https://agentmods.dev/instructions/ameyxd/petromcp/claude-md"><img src="https://agentmods.dev/badge/instructions/ameyxd/petromcp/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.02308 | $0.02308 |
| Opus 5 | $0.01154 | $0.01154 |
| Sonnet 5 | $0.00462 | $0.00462 |
| Haiku 4.5 | $0.00231 | $0.00231 |
Grade A, and why
petromcp 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 7d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
petromcp — project memory
What this is
An MCP server that exposes petroleum data formats (LAS, DLIS, SEG-Y, pump cards)
to Claude and other MCP-compatible hosts. Local-first. Synthetic data only by
default. The full spec lives at SPEC_petromcp.md in the repo root.
Where we are
v0.1 shipped on 2026-05-07 (tag 0.1). LAS slice only: three tools, QC prompt,
allowlist, synthetic generator, eval, Claude Desktop install, file-based access
log. 34 tests passing.
v0.1 design doc: docs/superpowers/specs/2026-05-06-petromcp-las-slice-design.md
v0.1 plan: docs/superpowers/plans/2026-05-06-petromcp-las-slice.md
v0.2 shipped on 2026-05-07 (tag 0.2). Added: compare_well_logs,
convert_units, four petromcp config subcommands, bad-LAS fixture corpus,
pyproject description trim. v0.2 design:
docs/superpowers/specs/2026-05-07-petromcp-v0.2-tier1-design.md. v0.2 plan:
docs/superpowers/plans/2026-05-07-petromcp-v0.2-tier1.md.
v0.3 (2026-05-08) shipped two bug fixes from the v0.2 bad-LAS corpus:
UTF-8 well names decode correctly via read_lasio; truncated LAS files
return a degraded LASSummary from read_las_file.
v0.4 (2026-07-26) is the public-distribution release: PyPI, Glama, and
Smithery. It also completes the v0.3 truncated-LAS fix, which only ever
covered read_las_file — summarize_las_curves and compare_well_logs
still raised IndexError, because the corpus tests only exercised one tool.
The guard now lives in utils/lasio_open.safe_index and every tool routes
through it. Also fixed: a half-specified depth interval was silently
dropped, serverInfo.version reported FastMCP's version, and __version__
had drifted from pyproject.
Publishing runbook: docs/PUBLISHING.md. Directory metadata lives in
glama.json, server.json, and packaging/mcpb/.
v0.5 (2026-07-26) replaces the sine-wave synthetic generator with a facies
model whose curves derive from the density-porosity and Wyllie relations,
adds a six-kind defect catalogue with an emitted ground-truth manifest, a
second well, eval scenario 02, and list_supported_units. Design:
docs/superpowers/specs/2026-07-26-petromcp-v0.5-synthetic-facies-design.md.
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.
- 7d ago First seen · 158 lines · 2,308 tokens per session scan A 712cd06c2ac0
petromcp CLAUDE.md is an instructions file published in the GitHub repository ameyxd/petromcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 2,308 tokens to every session, about $0.0115 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-31.
Other instructions, from other repositories
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).
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.
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.
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).
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.