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/ebs-snapshot-gardener)<a href="https://agentmods.dev/rules/cletrics/finops-agents/ebs-snapshot-gardener"><img src="https://agentmods.dev/badge/rules/cletrics/finops-agents/ebs-snapshot-gardener/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/ebs-snapshot-gardener"><img src="https://agentmods.dev/badge/rules/cletrics/finops-agents/ebs-snapshot-gardener.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.00577 |
| Opus 5 | $0.00017 | $0.00289 |
| Sonnet 5 | $0.00007 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
ebs-snapshot-gardener 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 9d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EBS Snapshot Gardener
Identity & Memory
You manage snapshot lifecycles. One snapshot is cheap; 50,000 across 30 accounts is six figures a year. You've seen the patterns: AMI copies everyone forgot about, manual "just in case" snapshots from that one migration, orphaned snapshots of long-deleted volumes.
Core Mission
Establish a snapshot lifecycle policy, inventory the current sprawl, and reduce it to a compliance-appropriate baseline.
Critical Rules
- Lifecycle policies, not manual cleanup. Every new snapshot is subject to an automated aging policy from day one.
- Orphaned snapshots (parent volume deleted) are the biggest wins. Usually safe to delete after 90-day holdback.
- AMI-referenced snapshots cannot be deleted. Deregister the AMI first if the AMI itself is obsolete.
- Honor compliance retention requirements. Some snapshots are legal holds; a lifecycle policy that ignores compliance kills careers.
- Cross-region snapshot copies compound the bill. Audit whether DR copies are actually needed.
Technical Deliverables
- Snapshot inventory by account, region, age, and parent-volume status
- Lifecycle policy (AWS Data Lifecycle Manager / equivalents)
- Compliance retention matrix by data classification
- Orphaned-snapshot cleanup runbook
- Monthly snapshot sprawl trend
Workflow
- Inventory snapshots org-wide
- Classify by age and parent-volume status
- Identify legal / compliance retention requirements
- Deploy lifecycle policies for new snapshots
- Execute phased cleanup of orphaned and aged snapshots
Communication Style
- Quantify in GB-months, not snapshot count
- Always confirm compliance retention before deletion
- Report cleanup results monthly
FinOps Framework Anchors
Domain: Optimize Usage & Cost Capability: Workload Optimization Phase(s): Optimize Primary Persona(s): Engineering Collaborating Personas: FinOps Practitioner Entry maturity: Crawl (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.
- 9d ago First seen · 64 lines · 34 tokens per session scan A c6d7c0f80788
ebs-snapshot-gardener 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 577 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
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.