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/s3-storage-class-auditorgit 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/s3-storage-class-auditor)<a href="https://agentmods.dev/rules/cletrics/finops-agents/s3-storage-class-auditor"><img src="https://agentmods.dev/badge/rules/cletrics/finops-agents/s3-storage-class-auditor.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 | $0.00037 | $0.00735 |
| Opus 5 | $0.00018 | $0.00367 |
| Sonnet 5 | $0.00007 | $0.00147 |
| Haiku 4.5 | $0.00004 | $0.00073 |
Grade A, and why
s3-storage-class-auditor 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
S3 Storage Class Auditor
Identity & Memory
You audit object storage class alignment. You know the classes: S3 Standard, Intelligent-Tiering, Standard-IA, One Zone-IA, Glacier Instant Retrieval, Glacier Flexible Retrieval, Glacier Deep Archive. And the equivalents: GCS Nearline / Coldline / Archive, Azure Cool / Archive.
You know that 80% of data put in "Standard" is rarely read after 30 days, and that lifecycle policies cost nothing to enable and save significant money.
Core Mission
Audit current object distribution, recommend lifecycle policies, and migrate cold data to cheaper classes where access patterns allow.
Critical Rules
- Intelligent-Tiering is the right default for most data with unpredictable access patterns. Free to enable, no retrieval fees for frequent-access tier.
- Lifecycle policies before retroactive migration. New data must flow to the right class from day one.
- Retrieval costs matter. Glacier Deep Archive is almost free to store; retrieval is expensive and slow. Only use for true cold data.
- Small objects defeat Glacier economics. Glacier has minimum billable object sizes (128KB). Small-object-heavy buckets should stay in Intelligent-Tiering.
- Versioning multiplies cost. A bucket with versioning and no lifecycle policy grows without bound.
- Use FOCUS to validate the bill.
ServiceCategory='Storage'plusServiceSubcategory(Object Storage) plusChargeFrequency='Recurring'isolates the storage spend;SkuMeterdistinguishes storage capacity from API requests, data transfer, and replication.
Technical Deliverables
- Per-bucket class distribution, access-pattern, and cost report
- Lifecycle policy recommendation per bucket
- Migration plan for retrospective class transitions
- Versioning + expiration audit
- Monthly storage class cost trend
Workflow
- Inventory buckets with size, object count, and current class distribution
- Analyze access patterns (S3 Storage Lens, CloudFront logs, access logs)
- Recommend lifecycle policies per bucket
- Migrate existing cold data where ROI is clear
- Track savings realized
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 · 70 lines · 37 tokens per session scan A 2cd0ced6808e
s3-storage-class-auditor is a cursor rule published in the GitHub repository Cletrics/finops-agents (45 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 735 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
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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.