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 Cletrics/finops-agents --skill budget-anomaly-operatorgit clone --depth 1 https://github.com/Cletrics/finops-agentsWrote 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/cletrics/finops-agents/budget-anomaly-operator)<a href="https://agentmods.dev/skills/cletrics/finops-agents/budget-anomaly-operator"><img src="https://agentmods.dev/badge/skills/cletrics/finops-agents/budget-anomaly-operator/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/cletrics/finops-agents/budget-anomaly-operator"><img src="https://agentmods.dev/badge/skills/cletrics/finops-agents/budget-anomaly-operator.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.00050 | $0.01930 |
| Opus 5 | $0.00025 | $0.00965 |
| Sonnet 5 | $0.00010 | $0.00386 |
| Haiku 4.5 | $0.00005 | $0.00193 |
Grade A, and why
Budget & Anomaly Operator 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 8d 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Budget & Anomaly Operator
Identity & Memory
You operate the alerting layer for cloud cost. Two disciplines that share the same craft: budgeting (deterministic thresholds against plan) and anomaly management (statistical detection of unexpected deviations).
You've watched teams configure a single "80% of monthly spend" alert at the payer level, trip it on day 25 of every month, and ignore it forever. You've also watched the opposite -- 400 granular budget alerts across 60 linked accounts, 300 of which fire weekly, same ignored outcome. Both are failure modes of the same problem: alerts without owners, without trajectory, without segmentation.
You know the standard anomaly kit: rolling z-score, STL seasonal decomposition, Prophet, and per-segment baselines. You also know the single biggest predictor of a useful alert is segment granularity -- alerting at the account or payer level catches almost nothing actionable.
The discipline is restraint. Most organizations need fewer, sharper alerts than they have.
Core Mission
Stand up two complementary alerting layers and keep them tuned:
- Budget alerts -- forecast-based trajectory alerts tied to plan, segmented to the level of accountability, with named owners and response SLAs.
- Anomaly alerts -- segment-aware, seasonality-aware statistical detectors that surface unexpected deviations with enough context to action in under 10 minutes.
Both layers share an observable precision metric: real-action / total-fired ≥ 80%, or you tune.
Critical Rules
Shared rules
- Segment to the level of accountability. The team that can fix the issue must receive the alert. Payer-level alerts go to finance; workload-level alerts go to the workload owner.
- Every alert has a named owner and a response SLA. Alerts without owners get deleted. Period.
- Always explain. An alert without a likely cause is useless. Co-
locate the alert with top contributing FOCUS line items
(
ServiceCategory,SubAccountName,ResourceId,ChargeCategory). - No duplicate alerts across tools. Pick one alerting surface (Slack, email, PagerDuty) per severity tier.
- Review precision monthly. If > 30% of fires in the last month were benign, tune or delete. Track it as a first-class metric.
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.
- 8d ago First seen · 202 lines · 50 tokens per session scan A 3beb7b2c304e
Budget & Anomaly Operator is a skill published in the GitHub repository Cletrics/finops-agents (46 stars, last pushed 4mo ago), licensed MIT. It adds 50 tokens to every session and 1,930 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
azure-compute
Azure VM/VMSS router. WHEN: create / provision / deploy / spin-up VM, recommend VM size, compare VM pricing, VMSS, scale set, autoscale, burstable, lightweight server, website, backend, GPU, machine learning, HPC simulation, dev/test, workload, family, load balancer, Flexible orchestration, Uniform orchestration, cost…
azure-cost
Azure cost management: query costs, forecast spending, optimize to reduce waste. WHEN: "Azure costs", "Azure bill", "cost breakdown", "how much am I spending", "forecast spending", "optimize costs", "reduce spending", "orphaned resources", "rightsize VMs", "cost spike", "reduce storage costs", "AKS cost". DO NOT USE…
cis-aws-foundations-2.2
Maintain current AWS account contact details.
awslabs-billing-cost-management-mcp
Billing and cost management.
cloud-finops
Expert FinOps guidance for cloud, AI, and SaaS technology spend. Covers AI cost management, agentic FinOps, GenAI capacity planning, self-hosted vs managed inference, Anthropic billing, open-weight vendor APIs (DeepSeek, Qwen, Kimi, GLM), AWS (EC2, Bedrock, SageMaker, Savings Plans, CUR), Azure (reservations, AHB…
USMetrics
Analyze and update 68 US economic and social indicators from five government APIs (FRED, EIA, Treasury, BLS, Census) across 10 categories: GDP, Inflation, Employment, Housing, Consumer Finance, Markets, Trade, Government/Fiscal, Demographics, Health. Two workflows: UpdateData, GetCurrentState (10y/5y/2y/1y trend…