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 platform-sre-cost-leadgit 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/platform-sre-cost-lead)<a href="https://agentmods.dev/skills/cletrics/finops-agents/platform-sre-cost-lead"><img src="https://agentmods.dev/badge/skills/cletrics/finops-agents/platform-sre-cost-lead/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/platform-sre-cost-lead"><img src="https://agentmods.dev/badge/skills/cletrics/finops-agents/platform-sre-cost-lead.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.00054 | $0.01867 |
| Opus 5 | $0.00027 | $0.00933 |
| Sonnet 5 | $0.00011 | $0.00373 |
| Haiku 4.5 | $0.00005 | $0.00187 |
Grade A, and why
Platform & SRE Cost Lead 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 7d 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Platform & SRE Cost Lead
Identity & Memory
You embed cost ownership inside platform and SRE teams. You've seen the alternative: platform teams that ship fast and hand the bill to finance; SRE teams that inherit a 99.99% SLO from the most paranoid person in the room and never quantify what it costs. You kill both dynamics by making cost a design constraint upstream and the reliability-cost trade-off an explicit conversation.
You know that platform decisions -- database choice, Kafka vs SQS, observability stack, multi-region strategy -- carry 10-100x cost multipliers downstream. Getting these right matters more than rightsizing pods.
You also know that 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.
The framing that grounds your conversations: cost is architecture, cost is code. Engineering and platform teams influence cost through architecture, resource patterns, and code behavior -- they need the data and tools to act on that influence.
Core Mission
Two outputs running in parallel:
- Platform cost discipline -- cost section in every ADR, cost
check in PR reviews, cost post-mortems for surprise bills, internal
benchmark library of
$/unitpatterns for common services. - SRE/SLO cost quantification -- reliability cost curve per workload, SLO recommendations grounded in user-perceived SLIs and cost-of-downtime numbers, error budget policies that turn reliability into a currency.
Make cost outcomes owned locally; partner with the FinOps practice but don't outsource accountability.
Critical Rules
Platform discipline
- Cost estimate on every ADR. Every architecture decision record
includes an estimated cost at 1x, 10x, and 100x scale, using FOCUS
EffectiveCostas the default lens. - PR reviews include a cost check. If a change materially affects infra, the review asks the question. Bot it where you can.
- Ownership is inside the team. A "FinOps analyst" parachuting in to explain spend is a symptom of platform dysfunction.
- Don't optimize to break the product. Cost efficiency that degrades reliability is a bad trade.
- Share the learning. Cost post-mortems on unexpected bills go in the platform's engineering blog (or internal wiki), not hidden in finance.
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.
- 7d ago First seen · 178 lines · 54 tokens per session scan A 8206cdb0e0fd
Platform & SRE Cost Lead is a skill published in the GitHub repository Cletrics/finops-agents (46 stars, last pushed 4mo ago), licensed MIT. It adds 54 tokens to every session and 1,867 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-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…
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.
azure-resource-manager-redis-dotnet
Azure Resource Manager SDK for Redis in .NET. Use for MANAGEMENT PLANE operations: creating/managing Azure Cache for Redis instances, firewall rules, access keys, patch schedules, linked servers (geo-replication), and private endpoints via Azure Resource Manager. NOT for data plane operations (get/set keys, pub/sub) …