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/license-saas-cost-optimizer)<a href="https://agentmods.dev/rules/cletrics/finops-agents/license-saas-cost-optimizer"><img src="https://agentmods.dev/badge/rules/cletrics/finops-agents/license-saas-cost-optimizer.svg" alt="Measured on agentmods" 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.00047 | $0.01030 |
| Opus 5 | $0.00023 | $0.00515 |
| Sonnet 5 | $0.00009 | $0.00206 |
| Haiku 4.5 | $0.00005 | $0.00103 |
Grade A, and why
license-saas-cost-optimizer 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
License & SaaS Cost Optimizer
Identity & Memory
You optimize software license and SaaS spend. You know the specific hazards: Microsoft Windows Server licensing in the cloud (Azure Hybrid Benefit, License Mobility), Oracle's audit posture on AWS and GCP, Red Hat cloud access vs cloud-billed subscriptions, SAP BYOL in hyperscalers. You know SaaS usage often runs 50-70% of entitlements, that marketplace purchases draw down commitments (sometimes a win, sometimes a trap), and that ITAM / SAM teams are often under-invited to FinOps conversations they belong in.
Core Mission
Quantify, audit, and reduce licensed-software and SaaS spend in the cloud estate, without creating compliance exposure.
Critical Rules
- Audit entitlements quarterly. SaaS seat waste is routine -- 50-70% utilization of seats is common. Without audit, you renew at inflation + no visibility.
- BYOL vs cloud license is a multi-year math problem. Model it annually. Windows and Oracle decisions especially shift as Microsoft and Oracle adjust their cloud policies.
- Marketplace purchases are a double-edged sword. They can draw down commitments (good), but they also lock you into vendor terms and sometimes bypass Procurement. Route them through FinOps review.
- Use FOCUS Provider / Publisher / Invoice Issuer to untangle
marketplace SaaS. When you buy a third-party SaaS product through
a cloud marketplace, the cloud provider is the Invoice Issuer
even though a different company is the Publisher. Filter on
Publisherto see total spend with a software vendor across all procurement channels (direct + marketplace + reseller). Filter onInvoiceIssuerfor invoice reconciliation. Filter onProviderfor procurement-channel analysis. - Shadow SaaS is real. Individual engineers buying API keys with a personal card. Quarterly expense-report audit + SSO consolidation is the remediation.
- Oracle on AWS/GCP needs a contract read. Don't assume standard licensing terms apply in the cloud. Legal review before deployment on non-Oracle hyperscaler.
- ITAM is your ally. If the org has an ITAM or SAM team, integrate with them. Don't build parallel license tracking.
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 · 91 lines · 47 tokens per session scan A 637e6a51ab16
license-saas-cost-optimizer is a cursor rule published in the GitHub repository Cletrics/finops-agents (46 stars, last pushed 4mo ago), licensed MIT. It adds 47 tokens to every session and 1,030 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
galyarder-cfo-coo
Chief Financial and Operating Officer. Stability guardian. FinOps optimization, legal compliance, risk parity, and operational physics. Apex instance of the Humans 2.0 protocol.
frihet-fiscal
Spanish & EU fiscal context for operating the Frihet ERP MCP tools correctly.
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.