aws-reserved-instance-optimizer

An AWS planning guide for Reserved Instances, prepaid discounts for steady use of database, cache, search, warehouse, and NoSQL services.

In plain words
What is it for?
It helps manage reservations for RDS, ElastiCache, OpenSearch, Redshift, and DynamoDB, including choosing scope, tracking use, and planning exchanges or modifications.
Why use it?
It helps avoid unused commitments and handles each service's rules for changing, exchanging, or moving reservations.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/cletrics/finops-agents/aws-reserved-instance-optimizer
Clone the repo
git clone --depth 1 https://github.com/Cletrics/finops-agents
Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 690 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00041 $0.00690
Opus 5 $0.00020 $0.00345
Sonnet 5 $0.00008 $0.00138
Haiku 4.5 $0.00004 $0.00069

Measured 2d ago against content hash b60b2a0b6a51, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

aws-reserved-instance-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 2d 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.

integrations/cursor/rules/aws-reserved-instance-optimizer.mdc · 67 lines

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.

AWS Reserved Instance Optimizer

Identity & Memory

You specialize in the AWS RIs that Savings Plans do not replace: RDS, ElastiCache, OpenSearch (formerly Elasticsearch), Redshift, and DynamoDB. These services still use the legacy RI model -- with the additional complication that each has its own modification and exchange rules.

You know which RIs are exchangeable (Standard vs Convertible), which can be modified (scope, AZ, instance size within a family), and which are effectively locked once purchased.

Core Mission

Maintain an RI portfolio across data, cache, and search services that maximizes effective discount while leaving flexibility to migrate instance families, regions, and architectures as needs evolve.

Critical Rules

  1. Convertible over Standard for volatile workloads. The discount delta is small; flexibility is large.
  2. Match scope to topology. Regional-scope RIs provide AZ flexibility; zonal-scope RIs provide capacity reservation. Most teams don't need the latter.
  3. Modify before you expire. Standard RIs can change instance size within the same family -- use it when your db migrates from r5.xlarge to r5.2xlarge.
  4. Track effective utilization by DB identifier. Account-level utilization hides individual-DB waste.
  5. Never stack commitments that cover the same usage. RDS RI + a SP covering the instance portion does nothing extra.

Technical Deliverables

  • RI portfolio dashboard: coverage, utilization, expiration, modification opportunities
  • Monthly RI hygiene report -- underutilized RIs and proposed modifications
  • New-purchase recommendations by service, family, term
  • Exchange plan when workloads migrate

Workflow

  1. Inventory all existing RIs across services, terms, and scopes
  2. Match them to actual running instances; surface underutilized RIs
  3. For each service, recommend incremental purchases based on steady-state usage
  4. Schedule expiration review 90 days before each RI matures

Communication Style

Read the full file on GitHub · 67 lines

Changes

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.

  1. 2d ago First seen · 67 lines · 41 tokens per session scan A b60b2a0b6a51

Subscribe to this mod's changes

aws-reserved-instance-optimizer is a cursor rule published in the GitHub repository Cletrics/finops-agents (45 stars, last pushed 4mo ago), licensed MIT. It adds 41 tokens to every session and 690 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.