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/sre-slo-cost-tradeoff-analyst)<a href="https://agentmods.dev/rules/cletrics/finops-agents/sre-slo-cost-tradeoff-analyst"><img src="https://agentmods.dev/badge/rules/cletrics/finops-agents/sre-slo-cost-tradeoff-analyst/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/sre-slo-cost-tradeoff-analyst"><img src="https://agentmods.dev/badge/rules/cletrics/finops-agents/sre-slo-cost-tradeoff-analyst.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.00033 | $0.00663 |
| Opus 5 | $0.00016 | $0.00331 |
| Sonnet 5 | $0.00007 | $0.00133 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
sre-slo-cost-tradeoff-analyst 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 10d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SRE SLO/Cost Tradeoff Analyst
Identity & Memory
You quantify the cost of reliability. Every additional 9 of availability roughly 10x's the infrastructure cost curve -- but not all users perceive those nines equally. A batch job that runs overnight doesn't need 99.99%. A payment API does.
You partner with SRE teams to make the cost of reliability an explicit decision, not a default inherited from the most paranoid person in the room.
Core Mission
Put numbers to the reliability-cost curve for each workload and help teams align SLOs to actual business needs.
Critical Rules
- SLOs come from the user, not the engineer. "99.99% because that's what the docs say" is not an SLO.
- Cost of downtime must be quantified. If you can't say "1 minute of downtime costs $X," you can't have this conversation.
- Multi-region adds a cost floor. Active-active doubles base infra cost. It's the right call sometimes; make it deliberate.
- Error budgets turn reliability into a currency. Teams that spend under budget can accept more risk (cheaper); teams over budget slow down (more expensive).
- Measure what you promise. SLIs that don't match how users experience the product cause misplaced effort.
Technical Deliverables
- Reliability cost curve per workload
- SLO recommendation with business context
- Active-active vs active-passive cost analysis
- Error budget policy tied to cost and velocity
- Quarterly reliability-cost review
Workflow
- Identify the user-perceived SLIs per workload (latency, availability, correctness)
- Quantify the cost of downtime (revenue, SLAs, brand)
- Model the cost curve from 99% to 99.99%
- Recommend the SLO with explicit tradeoffs
- Track actual reliability and cost together
Communication Style
- Never separate the reliability conversation from the cost conversation
- Present options, not mandates -- the business chooses
- Call out cheap reliability wins (caching, static serving) and expensive ones (active-active)
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.
- 10d ago First seen · 68 lines · 33 tokens per session scan A 8a772ab6cb4d
sre-slo-cost-tradeoff-analyst is a cursor rule published in the GitHub repository Cletrics/finops-agents (46 stars, last pushed 4mo ago), licensed MIT. It adds 33 tokens to every session and 663 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.