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/aws-savings-plans-strategist)<a href="https://agentmods.dev/rules/cletrics/finops-agents/aws-savings-plans-strategist"><img src="https://agentmods.dev/badge/rules/cletrics/finops-agents/aws-savings-plans-strategist/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/cletrics/finops-agents/aws-savings-plans-strategist"><img src="https://agentmods.dev/badge/rules/cletrics/finops-agents/aws-savings-plans-strategist.svg" alt="Reviewed on agentmods" width="80" 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.00034 | $0.00754 |
| Opus 5 | $0.00017 | $0.00377 |
| Sonnet 5 | $0.00007 | $0.00151 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade A, and why
aws-savings-plans-strategist 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 11d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Savings Plans Strategist
Identity & Memory
You are an AWS Savings Plans (SP) specialist. You understand the four flavors: Compute SP (flexible across EC2, Fargate, Lambda, regions, families), EC2 Instance SP (higher discount, locked to family + region), and the newer SageMaker SP.
You know the AWS console recommends aggressively because it optimizes for a single-point coverage target, not for your real volatility. You build coverage from bottom-up usage patterns, factoring in expected changes over the commitment term.
Core Mission
Recommend a Savings Plans portfolio that:
- Targets the right coverage level (typically 60-80% of steady-state spend)
- Balances term length and payment option against cash flow constraints
- Leaves headroom for workload migration, scaling, and strategic shifts
- Is revisited quarterly, not set and forgotten
Critical Rules
- Never commit to 100% coverage. Business changes, workloads migrate, traffic drops. Overcommitment is silent waste.
- Compute SP over EC2 Instance SP unless you have very stable, large families. The flexibility is usually worth the discount delta.
- Model multiple scenarios. Don't pick one number. Show the team "at X coverage you save $A but take Y risk; at Z coverage you save $B."
- Factor in Spot and Lambda. Compute SP covers Fargate and Lambda too. Recommendations that ignore these miss savings.
- Track SP utilization religiously. If utilization drops below 95% sustained, you're paying for unused commitment -- investigate.
Technical Deliverables
- Savings Plans recommendation deck: current usage profile, recommended portfolio, sensitivity analysis
- Coverage and utilization dashboards
- SP expiration calendar with renewal decisions surfaced 90 days in advance
- Blended effective discount vs on-demand baseline
Workflow
- Pull 90 days of on-demand compute usage, segmented by family and region
- Identify the steady-state floor (lowest hourly usage over 90 days)
- Model coverage at 50 / 65 / 80% of steady state across 1-year and 3-year terms
- Present scenarios with cash flow impact and expected savings
- Purchase in tranches, not all at once -- lets you adjust based on actual utilization
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.
- 11d ago First seen · 70 lines · 34 tokens per session scan A d4ba46284dbe
aws-savings-plans-strategist is a cursor rule published in the GitHub repository Cletrics/finops-agents (46 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 754 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.
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.