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 skills add Cletrics/finops-agents --skill sre-slo-cost-tradeoff-analystgit 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/skills/cletrics/finops-agents/sre-slo-cost-tradeoff-analyst)<a href="https://agentmods.dev/skills/cletrics/finops-agents/sre-slo-cost-tradeoff-analyst"><img src="https://agentmods.dev/badge/skills/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/skills/cletrics/finops-agents/sre-slo-cost-tradeoff-analyst"><img src="https://agentmods.dev/badge/skills/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.00043 | $0.00666 |
| Opus 5.5 | $0.00017 | $0.00266 |
| Sonnet 5.5 | $0.00009 | $0.00133 |
| Haiku 4.5 | $0.00004 | $0.00067 |
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 1mo 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 — 67 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.
- 1mo ago First seen · 67 lines · 43 tokens per session scan A 0a3121a54f53
SRE SLO/Cost Tradeoff Analyst is a skill published in the GitHub repository Cletrics/finops-agents (47 stars, last pushed 5mo ago), licensed MIT. It adds 43 tokens to every session and 666 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
cis-aws-foundations-2.2
Maintain current AWS account contact details.
azure-mgmt-applicationinsights-dotnet
Azure Application Insights SDK for .NET. Application performance monitoring and observability resource management. Use for creating Application Insights components, web tests, workbooks, analytics items, and API keys. Triggers: "Application Insights", "ApplicationInsights", "App Insights", "APM", "application…
azure-resource-manager-mysql-dotnet
Azure MySQL Flexible Server SDK for .NET. Database management for MySQL Flexible Server deployments. Use for creating servers, databases, firewall rules, configurations, backups, and high availability. Triggers: "MySQL", "MySqlFlexibleServer", "MySQL Flexible Server", "Azure Database for MySQL", "MySQL database…
scaffold
Generate deployment-ready infrastructure code from an architecture plan, verify it with adversarial self-review, and bridge to validation — all without deploying.
azure-mgmt-fabric-dotnet
Azure Resource Manager SDK for Fabric in .NET. Use for MANAGEMENT PLANE operations: provisioning, scaling, suspending/resuming Microsoft Fabric capacities, checking name availability, and listing SKUs via Azure Resource Manager. Triggers: "Fabric capacity", "create capacity", "suspend capacity", "resume capacity"…
azure-mgmt-mongodbatlas-dotnet
Manage MongoDB Atlas Organizations as Azure ARM resources using Azure.ResourceManager.MongoDBAtlas SDK. Use when creating, updating, listing, or deleting MongoDB Atlas organizations through Azure Marketplace integration. This SDK manages the Azure-side organization resource, not Atlas clusters/databases directly.