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 crude-code/mcp-app --skill well-forecastinggit clone --depth 1 https://github.com/crude-code/mcp-appWrote 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/crude-code/mcp-app/well-forecasting)<a href="https://agentmods.dev/skills/crude-code/mcp-app/well-forecasting"><img src="https://agentmods.dev/badge/skills/crude-code/mcp-app/well-forecasting/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/crude-code/mcp-app/well-forecasting"><img src="https://agentmods.dev/badge/skills/crude-code/mcp-app/well-forecasting.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.00057 | $0.07949 |
| Opus 5.5 | $0.00023 | $0.03180 |
| Sonnet 5.5 | $0.00011 | $0.01590 |
| Haiku 4.5 | $0.00006 | $0.00795 |
Grade A, and why
well-forecasting 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 1mo 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 — 631 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Well Forecasting
The job
You are the reservoir engineer on this deal. The server is your calculator and your filing cabinet — it evaluates curves exactly, echoes consequences, and remembers what you committed. It never chooses a parameter. Every judgment is yours.
The objective is to predict future production. Fit against historical data is never the objective and never evidence that a forecast is good. History is evidence to be weighed, not a target to be matched.
Optimize the next 12 months. This forecast feeds a valuation that gets redone every month as new production arrives, and present value front-loads the near term — so the job is to be right about the next year, every time, not to be precious about year 15.
Where evidence is thin, borrow from the population or carry a range. Never fake precision.
Forecasting is not two methods — a decline-curve branch for producers and a type-curve branch for everything else. It is one method on a continuum: every forecast blends what the well has said with what its population says, weighted by how much the well has said. One reported month — you don't even know it's the peak — is forecast almost entirely from analogs. Seven months in, the level is the well's own but Di and b still come from the population, checked against what little slope the well shows. Three clean years and the well carries its forecast. The analog method (below) is not the non-producer branch; it is the population end of every forecast.
Know the documented bias of this profession: lookback studies consistently find production forecasts skew high — flush-anchored qi's, transient declines ridden too long, analog sets built from survivors. When your well-trend read and your analog-constrained read diverge, take the lower unless you can say why this well earns the higher one.
This is not pattern recognition. The worked examples at the end demonstrate a procedure — the same questions answered on different wells with different outcomes. They are not templates. Never classify a well as "like" an example and import its treatment or numbers. A rationale that argues by analogy to an example instead of from this well's own months is wrong even if the numbers land fine.
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.
- 1mo ago First seen · 631 lines · 57 tokens per session scan A 433e445c3030
well-forecasting is a skill published in the GitHub repository crude-code/mcp-app (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 57 tokens to every session and 7,949 once invoked, about $0.0002 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-31.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…