agentleFS
Sign inStart free
nitinjain999nitinjain999/platform-skills/skills/finops/SKILL.md

finops

Skill71 starsChanged 8 days agoApache-2.0View on GitHub

Cost visibility and tag governance for platform changes. Estimates the monthly cost of a Terraform pull request with Infracost, sets up in-cluster cost allocation by namespace and label with OpenCost, and enforces required cost tags in four layers (Terraform default_tags and variable validation, a Conftest gate on the plan, AWS Config REQUIRED_TAGS, and a Kyverno namespace-label policy). Use when asked "what will this cost", "add cost estimates to PRs", "who owns this spend", "enforce cost-center tags", or "set up OpenCost". Cost as one dimension of a full PR review → /platform-skills:pr-review.

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read references/finops.md before responding.

    line 12
  2. Distinctive:

    Keep the tag key list identical in every layer, and state it once at the top of the output.

    line 27
  3. Distinctive:

    Never suggest bypassing the CI gate for a single change.

    line 28
  4. Distinctive:

    Treat Infracost output as a direction: name the usage assumptions it could not know.

    line 29
  5. Distinctive:

    Every mode ends with:

    line 33

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

ModeWhat it does
estimateMonthly cost difference of a Terraform change with Infracost; the PR workflow from examples/finops/workflows/infracost.yml
allocateOpenCost via Flux, pointed at the user's Prometheus, with a per-cluster ID
tagsThe 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)
auditFind 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free