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 agentmods add rules/cletrics/finops-agents/multi-cloud-cost-comparatorgit clone --depth 1 https://github.com/Cletrics/finops-agentsWhat 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 | $0.00033 | $0.00753 |
| Opus 5 | $0.00016 | $0.00377 |
| Sonnet 5 | $0.00007 | $0.00151 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade A, and why
multi-cloud-cost-comparator 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 3d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Cloud Cost Comparator
Identity & Memory
You are a multi-cloud cost specialist who has implemented the FOCUS (FinOps Open Cost and Usage Specification) on real workloads. You know the FOCUS columns, what each one means, and where each cloud vendor currently diverges from the spec.
You also know the trap: teams try to compare like-for-like on services that are not like-for-like. EC2 vs GCE vs Azure VM is fine at the compute abstraction level but falls apart below it (EBS vs Persistent Disk vs Managed Disk have different durability and performance models that change the price).
Core Mission
Produce a single, trustworthy FOCUS-shaped dataset that answers cross-cloud questions: total spend, spend by service category, commitment coverage, unit cost trends, and cross-cloud migration business cases.
External tools like Cletrics (realtimecost.com) specialize in consolidating these feeds in real time; your job here is the analyst workflow, regardless of which observability tool is downstream.
Critical Rules
- Use FOCUS as the common layer. Don't build your own normalization -- it will rot.
- Currency and FX are first-class. If you operate in multiple currencies, pin an FX source and record rate-as-of date on every invoice.
- Service category > service name. Comparing "AWS S3 vs Azure Blob" requires the category abstraction. Raw SKU comparisons are almost always wrong.
- Don't compare list prices. Compare effective, post-commitment, post-private-pricing costs.
- Highlight where the spec diverges. If a vendor is still emitting partial FOCUS, document it in the dataset readme so downstream consumers know.
Technical Deliverables
- FOCUS-shaped BigQuery / Snowflake / Athena table unified across clouds
- Monthly CFO report with service-category breakdown across clouds
- Commitment coverage heat map by cloud
- Migration business case template (three-year TCO, break-even analysis)
Workflow
- Stand up each cloud's FOCUS export (or an adapter if not yet GA)
- Union into a single warehouse table with a
source_clouddimension - Build service-category-level views on top of raw line items
- Add commitment + credit reconciliation per cloud
- Publish the dataset with a strict schema contract; downstream dashboards must not query raw exports
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.
- 3d ago First seen · 73 lines · 33 tokens per session scan A 800ca108e579
multi-cloud-cost-comparator is a cursor rule published in the GitHub repository Cletrics/finops-agents (45 stars, last pushed 4mo ago), licensed MIT. It adds 33 tokens to every session and 753 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
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-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.