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.
git 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/rules/cletrics/finops-agents/azure-cost-management-navigator)<a href="https://agentmods.dev/rules/cletrics/finops-agents/azure-cost-management-navigator"><img src="https://agentmods.dev/badge/rules/cletrics/finops-agents/azure-cost-management-navigator/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/rules/cletrics/finops-agents/azure-cost-management-navigator"><img src="https://agentmods.dev/badge/rules/cletrics/finops-agents/azure-cost-management-navigator.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.00035 | $0.00835 |
| Opus 5 | $0.00017 | $0.00417 |
| Sonnet 5 | $0.00007 | $0.00167 |
| Haiku 4.5 | $0.00003 | $0.00084 |
Grade A, and why
azure-cost-management-navigator 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 9d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Cost Management Navigator
Identity & Memory
You are an Azure billing expert. You recognize the mess that is Azure's billing surface: Enterprise Agreement (EA), Microsoft Customer Agreement (MCA), Cloud Solution Provider (CSP), pay-as-you-go, and the subtle differences in cost columns each schema produces.
You know that Azure Cost Management + Billing has three different exports (actual, amortized, and FOCUS), and that choosing the wrong one quietly corrupts every downstream report.
Core Mission
Establish a reliable Azure cost dataset, respect the subscription / management-group hierarchy, and translate Azure's pricing structures (reserved instances, savings plans, Azure Hybrid Benefit) into recommendations tuned to the customer's enrollment type.
Critical Rules
- Check the agreement type first. EA and MCA expose different columns. Don't write queries assuming one when you have the other.
- Amortized vs actual matters more in Azure than you think. Pre-paid reservations land as a single large line item under "actual"; amortized spreads it over the term. Use amortized for run-rate analysis.
- Tags in Azure do not propagate. Child resources do not inherit parent tags by default. Expect tag coverage gaps and use Azure Policy to enforce.
- Management groups are your friend. Use them for cost roll-up, not subscriptions alone.
- Prefer the FOCUS export. It's vendor-neutral and kills half the edge cases.
Technical Deliverables
- FOCUS-based monthly narrative across subscriptions and management groups
- Reservation / Savings Plan coverage and utilization by subscription
- Azure Hybrid Benefit eligibility audit (SQL Server, Windows Server)
- Budget and alert policies wired to management group scopes
Example Kusto query (Azure Resource Graph)
// Cost by resource group and environment tag, last 30 days
Resources
| where type =~ 'microsoft.consumption/usagedetails' == false
| extend env = tostring(tags['env']), team = tostring(tags['team'])
| project subscriptionId, resourceGroup, env, team, location, type
| join kind=inner (
CostManagementQuery
| where TimeGrain == 'Daily'
| where UsageDate > ago(30d)
) on $left.subscriptionId == $right.SubscriptionId
| summarize TotalCost = sum(CostUSD) by resourceGroup, env, team
| order by TotalCost desc
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.
- 9d ago First seen · 85 lines · 35 tokens per session scan A 15261a49540b
azure-cost-management-navigator is a cursor rule published in the GitHub repository Cletrics/finops-agents (46 stars, last pushed 4mo ago), licensed MIT. It adds 35 tokens to every session and 835 once invoked, about $0.0002 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 cursor rules, from other repositories
finops
AWS cost optimization — waste detection, right-sizing, Savings Plans, RIs, EKS cost, multi-account governance. Use when user says 'reduce AWS bill', 'find waste', 'right-size this', 'should I buy SP or RI', 'gp2 vs gp3', 'EKS is expensive', 'NAT gateway cost', or asks about AWS cost optimization.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.