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 finfocus-budgetgit 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/finfocus-budget)<a href="https://agentmods.dev/skills/rshade/finfocus/finfocus-budget"><img src="https://agentmods.dev/badge/skills/rshade/finfocus/finfocus-budget/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/finfocus-budget"><img src="https://agentmods.dev/badge/skills/rshade/finfocus/finfocus-budget.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.00098 | $0.01168 |
| Opus 5.5 | $0.00039 | $0.00467 |
| Sonnet 5.5 | $0.00020 | $0.00234 |
| Haiku 4.5 | $0.00010 | $0.00117 |
Grade A, and why
finfocus-budget 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FinFocus budgets
This skill is FinFocus-specific. Generic multi-tool budget workflows live in
rshade/agent-skills, not here.
1. Put the limit in config
finfocus config init writes $PROJECT/.finfocus/config.hujson inside a Pulumi
project, or ~/.finfocus/config.hujson otherwise. Project config overrides
global config at the top-level key. A legacy config.yaml is migrated on read.
Set cost.budgets. A global amount is required when any provider, tag, or type
budget is present. Amount 0 disables that scope. Only monthly is valid.
{
"cost": {
"budgets": {
"global": {
"amount": 500,
"currency": "USD",
"exit_on_threshold": true,
"exit_code": 2,
"alerts": [{ "threshold": 100, "type": "forecasted" }]
}
}
}
}
Full schema, scoped examples, and validation errors: references/budget-config.md.
2. See whether spend is inside the limit
finfocus cost projected --pulumi-json plan.json
finfocus cost actual --pulumi-json plan.json --from 2026-10-01
finfocus overview
Table output prints a BUDGET STATUS section. JSON and NDJSON cost documents
do not include that banner. Health bands:
- OK below 80%
- WARNING from 80% up to 90%
- CRITICAL from 90% up to 100%
- EXCEEDED at 100% and above
Several scopes roll up to the worst status.
Details: references/budget-health.md.
3. Fail CI only when asked
A global-only budget (no provider, tag, or type scope) exits through
checkBudgetExit. That path fails when exit_on_threshold is true and a
configured alert, including a forecasted alert, is exceeded.
--exit-on-threshold and --exit-code override the global scope for that one
command and write nothing to the config. FINFOCUS_BUDGET_EXIT_ON_THRESHOLD and
FINFOCUS_BUDGET_EXIT_CODE set cost.budgets.global for the process, and a
flag wins over them. Default is off, exit code 1.
What ships with it
4 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.
- 12d ago Changed · +1 lines 95e05ebe004e
- 13d ago First seen · 113 lines · 98 tokens per session scan A 471e76ec40b8
finfocus-budget is a skill published in the GitHub repository rshade/finfocus (10 stars, last pushed today), licensed Apache-2.0. It adds 98 tokens to every session and 1,168 once invoked, about $0.0004 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-03.
Other skills, from other repositories
dashboards
Use when creating or extending Costory dashboards, generating interesting FinOps overviews (suggestgroupby + suggestusagemetrics + text widgets), adding or replacing widgets, copying widgets between dashboards, editing dashboardContext (global filter / period / groupBy) via updatedashboard, or applying shared-context…
query
Use when exploring Costory cost, usage, metric, formula, budget, or external-metric data with the query tool — scope vs split (filterCel / groupBy), explorer PoP comparison, CEL discovery, unit economics, budgets. Not for one-shot "what changed last month" change trees — those use recipes explain-period-change /…
cost-change-investigation
Use when investigating a cost change to explain what changed, when, and the best-supported drivers with contribution, timing, usage, metric, event, alert, and terminology evidence. Call getskill with skillId "cost-change-investigation" before starting the investigation.
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…
costory-finops
Use when the user asks about cloud, Kubernetes, SaaS or AI spend through Costory: why a bill moved, cost by team/service/namespace, unit economics, budgets, allocating shared or untagged cost, or building Costory dashboards, scheduled reports and cost alerts. Covers org selection, the tool order, preview-then-confirm…
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'…