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 nitinjain999/platform-skills --skill finopsgit clone --depth 1 https://github.com/nitinjain999/platform-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/nitinjain999/platform-skills/finops)<a href="https://agentmods.dev/skills/nitinjain999/platform-skills/finops"><img src="https://agentmods.dev/badge/skills/nitinjain999/platform-skills/finops/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/nitinjain999/platform-skills/finops"><img src="https://agentmods.dev/badge/skills/nitinjain999/platform-skills/finops.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.00136 | $0.00585 |
| Opus 5.5 | $0.00054 | $0.00234 |
| Sonnet 5.5 | $0.00027 | $0.00117 |
| Haiku 4.5 | $0.00014 | $0.00059 |
Grade A, and why
finops 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 14d 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.
What it actually says
Make cost visible before a change merges, attributable after it runs, and impossible to leave untagged.
Read references/finops.md before responding. It holds the four-layer tag pattern and what each layer misses, the Infracost workflow and CLI, OpenCost configuration, and rollback. The working files are in examples/finops.
The required tag keys for this organisation are ${user_config.required_tag_keys}. If that reads as a literal placeholder or is empty, it is not configured: use owner, cost-center, environment and say so.
Mode dispatch
| Mode | What it does |
|---|---|
estimate |
Monthly cost difference of a Terraform change with Infracost; the PR workflow from examples/finops/workflows/infracost.yml |
allocate |
OpenCost via Flux, pointed at the user's Prometheus, with a per-cluster ID |
tags |
The four-layer tag enforcement for the user's keys: provider default_tags and validation, the Conftest policy and its tests, the AWS Config rule, the Kyverno policy (Audit first) |
audit |
Find untagged resources and unowned namespaces now: AWS Config compliance for REQUIRED_TAGS, namespaces missing cost labels, OpenCost's idle and unallocated cost |
Rules
- Keep the tag key list identical in every layer, and state it once at the top of the output.
- Never suggest bypassing the CI gate for a single change; fix the tags or change the rule in Git.
- Treat Infracost output as a direction: name the usage assumptions it could not know.
Output format
Every mode ends with:
- Changes, as exact files and fields
- Blast radius, in one line
- Validation, as commands (
opa test,conftest test,kubeconform,infracost diff) - Rollback
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.
- 14d ago First seen · 39 lines · 136 tokens per session scan A 61551e06b1d2
finops is a skill published in the GitHub repository nitinjain999/platform-skills (70 stars, last pushed today), licensed Apache-2.0. It adds 136 tokens to every session and 585 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-10-12.
Other skills, from other repositories
forge-cost
Audit cloud infrastructure costs and produce a concrete optimization plan with specific changes and estimated savings. Use when asked to "how much is this costing", "reduce cloud spend", "cost optimization", "are we overpaying", "cloud bill", or "budget for this infra".
brewpage-publish
Publish HTML, markdown, text, any file, or a multi-file site to brewpage.app — free hosting with no sign-up. Paste text, share a file, upload a site, or host a temporary page and get an instant public URL to share a link. Asks namespace and password, returns the public URL. Triggers: publish, publish HTML, share link…
terraform
Terraform and OpenTofu configuration, modules, testing, state management, and HCL review. Use for "terraform module", "terraform test", "infrastructure as code", "IaC", "HCL", "tfvars", "terraform plan", "terraform apply", "OpenTofu", "tftest", or multi-environment patterns.
pinescript
Pine Script v6 patterns: syntax rules, performance, debugging, backtesting, visualization. Use when asked to "write a Pine Script", "create an indicator", "build a strategy", "fix Pine code", or mentions PineScript, TradingView, indicator, strategy, or backtest.
health-check-endpoints
Implements liveness and readiness health check endpoints following Kubernetes probe conventions. Covers response schema, dependency checks, Kubernetes probe config, and circuit breaker integration. Invoked when the user asks to add health checks, implement a /health endpoint, or set up Kubernetes probes.
add-terraform-module
Scaffold a new Terraform module with variables, main, and outputs. Use when provisioning a new cloud resource (database, cache, storage, etc.) that needs its own Terraform module and optional IaC wrapper wiring.