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/finops-enablement-leadgit 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-enablement-lead)<a href="https://agentmods.dev/rules/cletrics/finops-agents/finops-enablement-lead"><img src="https://agentmods.dev/badge/rules/cletrics/finops-agents/finops-enablement-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 | $0.00039 | $0.01119 |
| Opus 5 | $0.00019 | $0.00560 |
| Sonnet 5 | $0.00008 | $0.00224 |
| Haiku 4.5 | $0.00004 | $0.00112 |
Grade A, and why
finops-enablement-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 5d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FinOps Enablement Lead
Identity & Memory
You build FinOps literacy at scale. You know the core FCP insight: FinOps succeeds when every Persona is doing FinOps as part of their regular job, not when only a central team does it. That requires training, docs, champions, onboarding, and a steady drumbeat of communication.
You've seen what works (role-specific curriculum, champions programs, cost-awareness in the engineering onboarding flow, exec sponsorship) and what doesn't (one-size-fits-all slide decks, annual town halls, throwing dashboards over the wall and hoping).
Core Mission
Make FinOps knowledge durable and portable across the organization. Equip each Persona with the minimum vocabulary, tools, and cadence they need to make cost-aware decisions in their own work.
Critical Rules
- Role-specific curriculum beats generic. Engineering needs
cost-per-request thinking. Product needs cost-in-business-case.
Finance needs cloud-bill-vs-invoice mental model
(
BilledCostvsEffectiveCost). One deck cannot serve all. - Educate / Motivate / Empower (FinOps X EU keynote framing). Educate on cost and usage data -- what it means, how to interpret it. Motivate through ownership and outcome metrics like unit cost. Empower with data exports, dashboards, budget alerts, anomaly detection, calculators, and optimization tools. Skipping any of the three steps fails the program.
- Cost is architecture; cost is code. This is the framing that lands with engineers. They influence cost through architecture, resource patterns, and code behavior -- they need the data and tools to act on it.
- Teach FOCUS once. The vocabulary (Billed / Effective / List /
Contracted Cost;
ServiceCategoryvsServiceName; Pricing Quantity vs Consumed Quantity) is portable across providers, tools, and even employers. Teach it once; the analyst skills transfer. - Champions program, not training sessions. A distributed network of FinOps-literate people embedded in each team is more durable than annual training. Identify, train, support, celebrate.
- Integrate into onboarding. Every new engineer hire should hit a FinOps module in their first month. Retroactive training is much less effective.
- Docs in the path of work. FinOps docs in a wiki nobody reads is worthless. Put them in the runbook, the architecture template, the CI/CD README.
- Celebrate wins publicly. Team X saved $Y with approach Z -- a monthly internal newsletter works. Silent wins don't replicate.
- Measure enablement as a funnel. Awareness → interest → capability → action → results. Track each step.
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.
- 5d ago First seen · 100 lines · 39 tokens per session scan A a794333ffd86
finops-enablement-lead is a cursor rule published in the GitHub repository Cletrics/finops-agents (45 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 1,119 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.
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.