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 ricmmartins/azure-sre-agent-skills --skill 04-finops-intelligencegit clone --depth 1 https://github.com/ricmmartins/azure-sre-agent-skillsWrote 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/ricmmartins/azure-sre-agent-skills/04-finops-intelligence)<a href="https://agentmods.dev/skills/ricmmartins/azure-sre-agent-skills/04-finops-intelligence"><img src="https://agentmods.dev/badge/skills/ricmmartins/azure-sre-agent-skills/04-finops-intelligence/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/ricmmartins/azure-sre-agent-skills/04-finops-intelligence"><img src="https://agentmods.dev/badge/skills/ricmmartins/azure-sre-agent-skills/04-finops-intelligence.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00055 | $0.03124 |
| Opus 5 | $0.00028 | $0.01562 |
| Sonnet 5 | $0.00011 | $0.00625 |
| Haiku 4.5 | $0.00006 | $0.00312 |
Grade A, and why
finops-intelligence 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 — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FinOps Intelligence
Purpose
Unified cost intelligence skill that identifies savings opportunities, tracks cost trends, and generates chargeback/showback reports by team or project. Answers both "where can we save?" and "who spent what?"
When to use this skill
- User asks "why did our bill go up?"
- User asks for cost optimization or savings opportunities
- User asks "how much did team X spend this month?"
- User asks for chargeback, showback, or cost allocation report
- Monthly proactive cost review or FinOps cadence
Pre-check
Confirm with the user:
- Scope: Which subscriptions to scan (all or specific ones)
- Time range: For trend analysis (default: last 3 months)
- Allocation model (for chargeback): Which tag to use for cost splitting?
cost-centertag (most common)ownerorteamtagapplicationorprojecttag- Resource group naming convention (e.g.,
rg-teamname-*)
- Exclusions: Dev/test subscriptions, sandbox resource groups
Analysis procedure
Step 1: Cost trend overview
Get the big picture using Azure Cost Management.
# Current month cost by service (last 30 days)
az costmanagement query --type ActualCost --timeframe MonthToDate \
--scope "subscriptions/<sub-id>" \
--dataset-aggregation '{"totalCost":{"name":"Cost","function":"Sum"}}' \
--dataset-grouping name="ServiceName" type="Dimension" \
-o table
# Previous month for comparison
az costmanagement query --type ActualCost --timeframe TheLastMonth \
--scope "subscriptions/<sub-id>" \
--dataset-aggregation '{"totalCost":{"name":"Cost","function":"Sum"}}' \
--dataset-grouping name="ServiceName" type="Dimension" \
-o table
If az costmanagement is unavailable, use the REST API:
az rest --method post \
--url "https://management.azure.com/subscriptions/<sub-id>/providers/Microsoft.CostManagement/query?api-version=2023-11-01" \
--body '{"type":"ActualCost","timeframe":"MonthToDate","dataset":{"aggregation":{"totalCost":{"name":"Cost","function":"Sum"}},"grouping":[{"type":"Dimension","name":"ServiceName"}]}}'
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 First seen · 272 lines · 55 tokens per session scan A 1001d94cc128
finops-intelligence is a skill published in the GitHub repository ricmmartins/azure-sre-agent-skills (70 stars, last pushed 18d ago), licensed MIT. It adds 55 tokens to every session and 3,124 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-08-30.
Other skills, from other repositories
budget-checker
Validates that a proposed trip fits within the user's stated budget.
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…
meter-chargeback
CocoMeter chargeback and FinOps governance. Usage: $meter chargeback refresh | $meter chargeback invoice | $meter chargeback onboarding.
meter-status
CocoMeter FinOps onboarding status. Usage: $meter status.
querying-well-data
How to query a Well workspace correctly — discover the schema first, then query the right root. Use whenever the user asks about their invoices, companies, contacts, bank transactions, accounts, or accounting ledger in Well, or before writing any wellqueryrecords call.