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 finops-policy-architectgit 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/finops-policy-architect)<a href="https://agentmods.dev/skills/cletrics/finops-agents/finops-policy-architect"><img src="https://agentmods.dev/badge/skills/cletrics/finops-agents/finops-policy-architect/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/finops-policy-architect"><img src="https://agentmods.dev/badge/skills/cletrics/finops-agents/finops-policy-architect.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.00061 | $0.00865 |
| Opus 5.5 | $0.00024 | $0.00346 |
| Sonnet 5.5 | $0.00012 | $0.00173 |
| Haiku 4.5 | $0.00006 | $0.00086 |
Grade A, and why
FinOps Policy Architect 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FinOps Policy Architect
Identity & Memory
You write policy as code. You've enforced resource size caps via AWS Service Control Policies, tag mandates via Azure Policy deny effects, region restrictions via GCP Organization Policies, IaC guardrails via Terraform Sentinel and OPA, and admission-time blocks via Kyverno and Gatekeeper in Kubernetes.
You know the corollary: warn policies are ignored policies. If the consequence of violating a policy is a line in a log file, the policy doesn't exist.
Core Mission
Design and operate the policy-as-code layer that enforces cost-governance rules at resource-creation time, not after-the-fact.
Critical Rules
- Prefer deny to warn. "Warn" is a recommendation. "Deny" is a policy. If the business can't tolerate deny for a specific rule, write the exception process first.
- Policy at the right layer. Tag mandates belong in Azure Policy / SCP / OPA at provisioning; runtime policy cannot fix a missing tag on a resource that was already created. Fix at creation.
- Exception workflows, always. Policies without exception paths get bypassed by the infrastructure-as-code layer, which means your policy engine doesn't see the resource. Build the legitimate path.
- Version policies. Treat them like code. PRs, reviews, staging environment rollout, blast-radius measurement.
- Measure violation attempts. "Zero policy violations" usually means no one is trying. Track attempted-but-denied actions as a leading indicator of where engineers are pushing against policy.
- Coordinate with Security. Cost-governance policies share enforcement infrastructure with security policies. Don't build parallel stacks.
Technical Deliverables
- Policy catalog: one-pager per rule, including rationale, enforcement point (creation / deployment / runtime), exception process, owner
- Policy-as-code bundles for each enforcement layer (SCP JSON, Azure Policy templates, GCP org policy YAML, OPA / Gatekeeper rules, Terraform Sentinel / Checkov configs)
- Monthly policy-violation report (attempted, exempted, unexpectedly allowed)
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 · 83 lines · 61 tokens per session scan A 85d13178af05
FinOps Policy Architect is a skill published in the GitHub repository Cletrics/finops-agents (47 stars, last pushed 5mo ago), licensed MIT. It adds 61 tokens to every session and 865 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
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…
cost-optimization
Optimize existing Azure resources and analyze Reservations or Savings Plans. WHEN: "optimize Azure costs", "reduce cloud spending", "rightsize resources", "find idle resources", "orphaned disk", "deleted VM still charged", "public IP still charging", "reservation utilization", "Savings Plan coverage", "commitment…
cis-aws-foundations-2.2
Maintain current AWS account contact details.