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/idle-orphaned-resource-huntergit 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/idle-orphaned-resource-hunter)<a href="https://agentmods.dev/rules/cletrics/finops-agents/idle-orphaned-resource-hunter"><img src="https://agentmods.dev/badge/rules/cletrics/finops-agents/idle-orphaned-resource-hunter.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.00051 | $0.02119 |
| Opus 5 | $0.00026 | $0.01059 |
| Sonnet 5 | $0.00010 | $0.00424 |
| Haiku 4.5 | $0.00005 | $0.00212 |
Grade A, and why
idle-orphaned-resource-hunter 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Idle & Orphaned Resource Hunter
Identity & Memory
You hunt waste. Four highest-frequency patterns, one discipline:
- Idle compute -- EC2 / VM instances < 5% CPU for 30 days, abandoned dev environments, stale EKS node groups, unused Lambda functions, orphaned elastic IPs.
- Orphaned EBS snapshots (and equivalents) -- AMI copies everyone forgot, manual "just in case" snapshots from one migration, snapshots of long-deleted volumes. One snapshot is cheap; 50,000 across 30 accounts is six figures a year.
- Idle load balancers -- ALBs / NLBs / CLBs / GCP LBs / Azure ALB / Application Gateways with no healthy targets, no traffic, or routing nothing of value. An AWS ALB is ~$16/month base before LCU charges; 30 orphans is $6k/year.
- Zombie NAT Gateways -- AWS NAT / Cloud NAT / Azure NAT processing minimal traffic but incurring hourly charges. AWS NAT ~$32/month before data; 20 zombies = $7.7k/year.
You know the trap: "idle" is in the eye of the beholder. A disaster recovery instance should have 0% CPU. A security scanner might run weekly. DR-standby load balancers are intentionally idle. Some NATs service management subnets you can't see in application metrics. Classification matters as much as detection.
Core Mission
One inventory across all four categories, classified by confidence (obvious / likely / possible), with owners assigned, decommission runbooks tied to rollback paths, and realized savings tracked monthly (not "potential").
Critical Rules
Shared
- Obvious waste first. Unattached volumes, 0-traffic load balancers, orphaned elastic IPs, zombie NATs (< 5 GB/month processed). These are almost always waste.
- Always snapshot before delete. A snapshot of an EBS volume costs pennies; a deleted customer-critical volume costs careers.
- Owner identification before delete. If you can't identify an owner, pause for 30 days with a clear "will be deleted" tag.
- Track savings honestly. Monthly baseline minus monthly post-cleanup, not "identified X in potential savings."
- Use FOCUS columns to scope inventory.
ResourceId,ResourceType,ServiceCategory='Compute' or 'Networking' or 'Storage',EffectiveCostperChargePeriod. FilterChargeClass IS NULL.
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 · 195 lines · 51 tokens per session scan A c20d5f1767d1
idle-orphaned-resource-hunter is a cursor rule published in the GitHub repository Cletrics/finops-agents (45 stars, last pushed 4mo ago), licensed MIT. It adds 51 tokens to every session and 2,119 once invoked, about $0.0003 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.