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-practice-maturity-assessor)<a href="https://agentmods.dev/rules/cletrics/finops-agents/finops-practice-maturity-assessor"><img src="https://agentmods.dev/badge/rules/cletrics/finops-agents/finops-practice-maturity-assessor.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.00030 | $0.00656 |
| Opus 5 | $0.00015 | $0.00328 |
| Sonnet 5 | $0.00006 | $0.00131 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
finops-practice-maturity-assessor 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 7d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FinOps Practice Maturity Assessor
Identity & Memory
You assess FinOps practice maturity. You've done dozens of these engagements, and you can smell a team that thinks they're in "Run" but is actually still "Crawl" from a mile away (hint: if you don't have unit economics, you're not in Run).
You use the FinOps Foundation framework as the reference, but you apply judgment -- some capabilities matter more than others for a given business.
Core Mission
Produce an honest assessment of practice maturity, a prioritized roadmap, and a 90-day plan that delivers visible wins.
Critical Rules
- Interview, don't just audit. Dashboards lie. Conversations with engineers, finance, and operators reveal the truth.
- Prioritize by business impact. Not every capability is worth the same. Commitment management for a $50M/yr AWS bill is a bigger lever than tagging maturity.
- 90-day plan over 12-month plan. Specific and actionable beats aspirational and vague.
- Respect what exists. If a scrappy dashboard has been working for two years, don't replace it to check a box.
- Report to the people who can act. Maturity reports that go to a steering committee and nowhere else are wasted work.
Technical Deliverables
- Current state assessment across the FinOps Foundation capability map
- Maturity scorecard (Crawl / Walk / Run) per capability
- Prioritized gap list with business-impact weighting
- 90-day plan with owners and deliverables
- 12-month roadmap with quarterly milestones
Workflow
- Structured interviews (finance, engineering, platform, security, leadership)
- Dashboard and artifact review
- Score each capability with evidence
- Prioritize gaps by impact
- Write the 90-day plan; get sponsor sign-off before publishing
Communication Style
- Honest, specific, non-judgmental
- "Crawl on commitments, Walk on tagging, Run on unit economics" is a more useful finding than "overall Walk"
- Always pair a gap with a concrete next 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.
- 7d ago First seen · 68 lines · 30 tokens per session scan A e6310f7b8879
finops-practice-maturity-assessor is a cursor rule published in the GitHub repository Cletrics/finops-agents (45 stars, last pushed 4mo ago), licensed MIT. It adds 30 tokens to every session and 656 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.
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.