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 selvarajmurugesan90/ops-engineering-skills --skill cloud-cost-finops-optimizationgit clone --depth 1 https://github.com/selvarajmurugesan90/ops-engineering-skillsWrote 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/selvarajmurugesan90/ops-engineering-skills/cloud-cost-finops-optimization)<a href="https://agentmods.dev/skills/selvarajmurugesan90/ops-engineering-skills/cloud-cost-finops-optimization"><img src="https://agentmods.dev/badge/skills/selvarajmurugesan90/ops-engineering-skills/cloud-cost-finops-optimization/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/selvarajmurugesan90/ops-engineering-skills/cloud-cost-finops-optimization"><img src="https://agentmods.dev/badge/skills/selvarajmurugesan90/ops-engineering-skills/cloud-cost-finops-optimization.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.00119 | $0.02960 |
| Opus 5.5 | $0.00048 | $0.01184 |
| Sonnet 5.5 | $0.00024 | $0.00592 |
| Haiku 4.5 | $0.00012 | $0.00296 |
Grade A, and why
cloud-cost-finops-optimization 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloud Cost & FinOps Optimization
Purpose
Cloud spend left ungoverned grows faster than the value it produces — not because any one decision was wrong, but because pay-as-you-go pricing removes the natural friction that used to force capacity planning conversations. FinOps closes that gap by making cost a first-class, continuously reviewed signal: every resource attributable to a team and purpose, every commitment decision (Reserved Instances, Savings Plans, Committed Use Discounts) made deliberately rather than defaulted to on-demand, and every anomaly caught within days, not discovered at month-end reconciliation. This skill covers the recurring, cross-cloud practices — tagging, rightsizing, commitment strategy, showback/ chargeback, and anomaly response — that turn cost from a lagging indicator into an operating input.
When to use
- Standing up cost allocation (tagging/labeling) so spend can be attributed to teams, products, or cost centers.
- Investigating a month-over-month cost increase or an anomaly alert.
- Deciding between commitment-based discount instruments (Reserved Instances vs. Savings Plans on AWS; Reserved VM Instances vs. Azure Savings Plans; Committed Use Discounts on GCP) for a stable workload.
- Rightsizing over-provisioned compute, storage, or database instances.
- Building a showback or chargeback dashboard so teams see (and are accountable for) their own spend.
- Responding to finance/leadership asking "why did the bill go up" or "what's our unit economics per customer/transaction."
Prerequisites & environment
- Billing/cost data access: AWS Cost Explorer + Cost and Usage Report (CUR) in a dedicated S3 bucket, Azure Cost Management + Billing scoped to the relevant Management Group/subscription, or GCP Billing export to BigQuery — set these up before anything else; you cannot optimize what you can't see broken down by resource and tag/label. ("Symptom/Fix" for what happens without this is below.)
- A tagging/labeling taxonomy agreed with stakeholders (minimum viable
set:
cost-center,environment,owner,service) enforced via the landing-zone guardrails (AWS tag policies + SCP, Azure Policy, GCP Organization Policy / labels) — see the respective landing-zone skills. - For commitment purchases: at least 30-90 days of historical usage data per instance family/region to size commitments against real, not guessed, baseline usage.
- Optional but recommended: a FinOps tool (CloudHealth, Cloudability, Kubecost for Kubernetes-specific allocation, or the open-source OpenCost) if spend is complex enough that native cost-explorer tools become unwieldy across multiple accounts/subscriptions/projects.
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 · 250 lines · 119 tokens per session scan A 534bcc0f1c4f
cloud-cost-finops-optimization is a skill published in the GitHub repository selvarajmurugesan90/ops-engineering-skills (42 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 119 tokens to every session and 2,960 once invoked, about $0.0005 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-08-30.
Other skills, from other repositories
aws-cost-operations
AWS cost optimization, monitoring, and operational excellence expert. Use when analyzing AWS bills, estimating costs, setting up CloudWatch alarms, querying logs, auditing CloudTrail activity, or assessing security posture.
aws-cost-cleanup
Automated cleanup of unused AWS resources to reduce costs.
azure-compute
Azure VM/VMSS router. WHEN: create / provision / deploy / spin-up VM, recommend VM size, compare VM pricing, VMSS, scale set, autoscale, burstable, lightweight server, website, backend, GPU, machine learning, HPC simulation, dev/test, workload, family, load balancer, Flexible orchestration, Uniform orchestration, cost…
azure-cost
Azure cost management: query costs, forecast spending, optimize to reduce waste. WHEN: "Azure costs", "Azure bill", "cost breakdown", "how much am I spending", "forecast spending", "optimize costs", "reduce spending", "orphaned resources", "rightsize VMs", "cost spike", "reduce storage costs", "AKS cost". DO NOT USE…
cost-estimation
Forecast Azure spend and price planned resources or workloads. WHEN: "forecast Azure spending", "project next month cost", "compare forecast to my planning target", "how much will Azure cost", "estimate VM cost", "compare storage tiers", "compare Azure regions", "retail price", "EA rate card", "negotiated pricesheet".…
cost-governance
Govern Azure costs with budgets, alerts, tags, and policy restrictions. WHEN: "Azure budget health", "configured budget overrun", "list Azure budgets", "create Azure budget", "budget alerts", "budget coverage", "missing CostCenter tags", "allowed VM SKUs", "allowed Azure regions", "would this SKU be denied", "cost…