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 statement-checkupgit 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/statement-checkup)<a href="https://agentmods.dev/skills/crude-code/mcp-app/statement-checkup"><img src="https://agentmods.dev/badge/skills/crude-code/mcp-app/statement-checkup/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/statement-checkup"><img src="https://agentmods.dev/badge/skills/crude-code/mcp-app/statement-checkup.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.00000 | $0.02848 |
| Opus 5.5 | $0.00000 | $0.01139 |
| Sonnet 5.5 | $0.00000 | $0.00570 |
| Haiku 4.5 | $0.00000 | $0.00285 |
Grade A, and why
statement-checkup 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Statement Checkup
What you're doing
The user is an individual mineral or royalty owner — usually not an oil & gas professional — holding a revenue statement (the detail pages behind a royalty check) that they find hard to read. Your job is a health check: read the statement, verify it against public data, explain where the money went, and surface anything worth a question to the operator — all in plain English.
This is NOT the dataroom flow and NOT a valuation. dataroom-extract is for
an acquisition package headed to a bid; this is one owner's check. If the
user later asks what their interest is worth, that's a follow-up — offer
the valuation flow then, never as part of the checkup.
Who you're writing for
- Plain English, dollars first. "Fees for moving gas took $47.77 out of your check," not "post-production cost burden of 101% of gas revenue." Define each term of art inline, once ("severance tax — the state's tax on produced minerals").
- Reassure where things are normal. Most statements are normal, and the owner can't tell — saying "this part checks out, and here's how I checked" is half the product's value.
- Questions, never accusations. A negative gas line is a fact about the statement; whether it's proper depends on lease language you can't see. Frame every issue as a question for the operator, never as a claim of underpayment.
What you're building toward
Three small JSON files and one artifact, with all arithmetic done by the bundled script — never by you:
statement.json— the extraction (schema below; worked synthetic example inexample.json).public.json— state-reported volumes + benchmark prices, pulled withrun_sql.findings.json— the judgment layer: findings, questions, notes — written by you AFTER reading the script's--factsdigest.checkup_payload.pyties the extraction out against the statement's own printed totals and computes every rollup; its output fillsStatementCheckup.jsx(the finished, frozen viewer — you do not build, redesign, or adapt it) asDATA/TITLE/TLDR.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 213 lines · 0 tokens per session scan A 2f31fc02a7e3
statement-checkup is a skill published in the GitHub repository crude-code/mcp-app (5 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,848 tokens. 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
sector-rotation
An analysis framework for comparing industries in the Chinese A-share stock market, using business conditions, price momentum, valuation, and money flows. It produces rankings and higher- or lower-allocation suggestions.
twitter-reader
Read Twitter/X for financial research through opencli: the user's home timeline, tweet search, trending topics, bookmarks, a user's recent tweets, threads, articles, profiles, followers and following, and notifications. Use this skill whenever the user wants to know what people are saying on Twitter/X or fintwit about…
strategy-pivot-designer
Detect backtest iteration stagnation and generate structurally different strategy pivot proposals when parameter tuning reaches a local optimum.
energy-procurement
Codified expertise for electricity and gas procurement, tariff optimization, demand charge management, renewable PPA evaluation, and multi-facility energy cost management. Informed by energy procurement managers with 15+ years experience at large commercial and industrial consumers. Includes market structure analysis…
airdrop-hunting-guide
Guide to finding and qualifying for crypto airdrops — eligibility criteria, farming strategies, on-chain activity requirements, Sybil detection avoidance, and tracking tools. Use when helping users understand airdrops, check eligibility, or plan participation strategies.
china-portfolio-monitoring
A monitoring framework for tracking the financial results, operating measures, strategic milestones, and risks of companies held by China-focused private-equity funds. It uses measures such as revenue growth, margins, debt, cash flow, and return on equity.