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 rshade/finfocus --skill cost-checkgit clone --depth 1 https://github.com/rshade/finfocusWrote 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/rshade/finfocus/cost-check)<a href="https://agentmods.dev/skills/rshade/finfocus/cost-check"><img src="https://agentmods.dev/badge/skills/rshade/finfocus/cost-check/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/rshade/finfocus/cost-check"><img src="https://agentmods.dev/badge/skills/rshade/finfocus/cost-check.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.00131 | $0.01562 |
| Opus 5.5 | $0.00052 | $0.00625 |
| Sonnet 5.5 | $0.00026 | $0.00312 |
| Haiku 4.5 | $0.00013 | $0.00156 |
Grade A, and why
cost-check 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 today.
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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cost Check
Run finfocus cost projected on the current project, apply thresholds, and
write COST_CHECK.md.
Install: npx skills add rshade/finfocus -s cost-check.
Required CLI: finfocus v0.5.0 or newer. Update this line with the release the skill was last run against.
Core principle: read the numbers the CLI returns. Never estimate a price
by hand, never parse the table output, and never report an unpriced resource
as $0.
1. Detect the input
| Found in the project | Input | Status |
|---|---|---|
Pulumi.yaml or Pulumi.yml (this directory or a parent) |
--pulumi-json plan.json, or auto-detect |
supported |
terraform.tfstate |
--terraform-state terraform.tfstate |
supported, state only |
*.tf with no state file |
none | not supported: Terraform plan input is not available as of v0.5.0 |
Terraform: the CLI prices what is in the state file, so a state that does not
exist yet or is stale gives no estimate for the pending change. Say so in the
report. Do not run terraform plan and do not convert its output. When
Terraform plan input ships, edit this table and references/cli-contract.md.
If a Pulumi project and a Terraform state are both present, run each separately. If nothing is found, stop: "No Pulumi project or Terraform state found in this directory."
2. Preflight
command -v finfocus
finfocus --version
finfocus plugin list --output json
- No binary: stop, name the failure, point to the
finfocus-installskill. - Version older than the required one: stop and print both versions. A build
such as
v0.5.0-6-g3cb7dedcounts as v0.5.0. An unparseable version, or0.1.0with no leadingv(an unstamped source build), continues, and the report says "version unverified". plugin listreturns[]: no plugin is installed. Continue.cost projectedcan still price resources from local YAML specs, so an empty list does not mean nothing is priced. Step 5 decides whether an estimate exists. Point tofinfocus-installfor the missing prices.
What ships with it
5 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.
- today Changed · +4 lines f61e8a50c4b9
- yesterday First seen · 135 lines · 131 tokens per session scan A 6ff2eb7e028b
cost-check is a skill published in the GitHub repository rshade/finfocus (10 stars, last pushed today), licensed Apache-2.0. It adds 131 tokens to every session and 1,562 once invoked, about $0.0005 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-10-20.
Other skills, from other repositories
recipes
Use when a user states a FinOps outcome rather than a tool. Route to one recipe card, then hand off: bill jump → explain-period-change (DIGEST preview); clicked chart slice / explain this bar → explain-chart-slice; marketplace → marketplace-spend; K8s namespace → namespace-cost; credits runway → provider-credits; GCP…
cost-optimization
Cloud Cost Optimization & FinOps: Helps analyze and reduce cloud infrastructure costs, optimize resource usage, implement FinOps practices, and find savings opportunities. Use whenever the user mentions 'cloud costs', 'AWS bill', 'cost optimization', 'FinOps', 'right-sizing', 'reserved instances', 'savings plans'…
aws-cost-ops
AWS Cost Explorer — spending analysis, service breakdowns, forecasts, cost anomalies. Use when analyzing AWS spending, investigating cost spikes, reviewing network cost drivers like NAT Gateway, or forecasting next month's bill.
finops-expert
Expert-level cloud financial operations, cost optimization, and cloud economics. Use when the user mentions cloud cost, optimization, cloud economics, or AWS cost, or when the task involves FinOps Fundamentals, Cost Management, FinOps Practices, or Cost Visibility.
cloud-costs
Use nable's cost tools when the user asks what something costs, why a cloud or AI bill went up, what their AI coding spend is, or before launching, resizing or destroying infrastructure. Also explains how to respond when the nable guard asks for confirmation before a command runs.
credits-runway
Use before launching GPU or other large cloud resources at a startup running on cloud credits, or when asked how long the credits will last.