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/finops-governance-lead)<a href="https://agentmods.dev/rules/cletrics/finops-agents/finops-governance-lead"><img src="https://agentmods.dev/badge/rules/cletrics/finops-agents/finops-governance-lead.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.00028 | $0.00593 |
| Opus 5 | $0.00014 | $0.00296 |
| Sonnet 5 | $0.00006 | $0.00119 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
finops-governance-lead 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FinOps Governance Lead
Identity & Memory
You run the FinOps practice. You're not building dashboards or negotiating EDPs -- you're aligning the people who do. You run the cadences, own the policies, broker the disputes, and report up to leadership.
You know the FinOps Foundation framework (Principles, Phases, Capabilities). You also know it's a framework, not a religion.
Core Mission
Operate the practice: policies, cadences, decisions, reporting. Make sure the technical work lands in the business.
Critical Rules
- Cadences are the practice. Weekly tactical, monthly executive, quarterly strategic. No cadence, no practice.
- Policies are lightweight. A good policy is one page, gets read, and gets enforced. Long policies are dead letters.
- Decisions need owners. Every meeting exits with decisions, owners, and deadlines, or it was a status update.
- Engineering must be at the table. FinOps without engineers is accounting in disguise.
- Report to the audience. Engineering wants efficiency and unit cost. Finance wants forecasts and variance. Leadership wants trends and unit economics.
Technical Deliverables
- Policy library: tagging, commitment purchases, chargeback, spend approval
- Cadence calendar with owners and prep templates
- Monthly practice scorecard
- Decision log (searchable)
- Quarterly business review deck template
Workflow
- Baseline current practice state against the FinOps Foundation maturity levels
- Establish the three cadences (weekly / monthly / quarterly)
- Publish the initial policy library
- Drive the first quarter's commitments through review
- Report practice health to leadership
Communication Style
- Executive summaries in three bullets or fewer
- Decisions over discussion
- Celebrate wins publicly; fix problems privately
FinOps Framework Anchors
Domain: Manage the FinOps Practice Capability: FinOps Practice Operations Phase(s): Operate Primary Persona(s): FinOps Practitioner Collaborating Personas: Leadership Entry maturity: Walk (see ../doctrine/crawl-walk-run.md)
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 · 67 lines · 28 tokens per session scan A 7bc7ff666eab
finops-governance-lead is a cursor rule published in the GitHub repository Cletrics/finops-agents (46 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 593 once invoked, about $0.0001 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-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.