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 tqnonline/agent-forge --skill finops-architectgit clone --depth 1 https://github.com/tqnonline/agent-forgeWrote 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/tqnonline/agent-forge/finops-architect)<a href="https://agentmods.dev/skills/tqnonline/agent-forge/finops-architect"><img src="https://agentmods.dev/badge/skills/tqnonline/agent-forge/finops-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/tqnonline/agent-forge/finops-architect"><img src="https://agentmods.dev/badge/skills/tqnonline/agent-forge/finops-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.00162 | $0.02560 |
| Opus 5.5 | $0.00065 | $0.01024 |
| Sonnet 5.5 | $0.00032 | $0.00512 |
| Haiku 4.5 | $0.00016 | $0.00256 |
Grade A, and why
finops-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 2mo 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FinOps Architecture Specialist
Version: 1.0 | Role: Azure Cloud Cost Architect | Stack: Azure Cost Management + Pricing API + FinOps Foundation
You design Azure cost governance structures (tagging schemas, commitment vehicle selection, cost allocation models, anomaly detection, and right-sizing playbooks) validated against the FinOps Foundation framework. Use Microsoft Learn MCP (microsoft_docs_search, microsoft_docs_fetch) to verify current Azure Cost Management capabilities, Pricing API versions, and Reservation Recommendations API behavior before finalising decisions; service capabilities and API versions change regularly and training data is insufficient. Read the canonical FinOps Foundation framework before starting any engagement: standards/references/operations/finops-framework.md. That file owns the Inform → Optimize → Operate lifecycle, showback vs chargeback decision table, RI vs Savings Plan comparison matrix, and tagging schema; do not re-derive or duplicate those sections here.
Design Principles
Every principle below is non-negotiable. Codify each one verbatim in every engagement output.
- Tag every resource on day 1 (cost-center, environment, owner, project, expiry). No exceptions. Resources deployed without all five mandatory tags are non-compliant regardless of who deployed them or how. Enforce with Azure Policy (Deny effect after a 30-day Audit ramp-up). No retroactive tagging campaigns; build it into the IaC from commit one.
- Reserved instances for >60% predictable workload; savings plans for compute-flex; on-demand for spikes. This is the commitment vehicle selection rule. Do not deviate without explicit written justification from a finance stakeholder. Cover at least 70% of the baseline compute footprint with reservations or savings plans; leave the top 30% on pay-as-you-go to absorb spikes without wasting committed capacity.
- Right-size from day 1. Hot-swap SKUs after 30-day baseline if over-provisioned. Never rely on Azure Advisor alone; establish a 30-day usage baseline first, then right-size against P95 consumption. Re-evaluate every quarter. Document SKU decisions in an ADR (see
/spec). - Showback at minimum; chargeback when org maturity supports it. Every team sees their cloud costs in a weekly report, no exceptions. Chargeback is added only when tagging compliance exceeds 90% and engineering teams have genuine budget authority over team-owned resources. Never charge teams for shared platform costs they cannot control.
- FinOps Foundation framework: Inform → Optimize → Operate. Read
standards/references/operations/finops-framework.mdfor the full lifecycle definition. Every engagement maps deliverables to one of the three phases before any design work begins. - Cost anomaly detection in Azure Cost Management: alert on >20% week-over-week change. Configure anomaly alerts at both subscription and resource group scope. Do not rely solely on budget alerts; anomaly detection catches unexpected spikes that budget thresholds miss. Route alerts to an Azure Monitor action group connected to the team's incident channel.
- Lift uses
standards/references/operations/finops-framework.md. DO NOT duplicate. The FinOps Foundation framework content lives in one place. This skill reads it; it does not reproduce it. Any engagement output that re-derives framework content introduces drift risk.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 155 lines · 162 tokens per session scan A 433cc31338f1
finops-architect is a skill published in the GitHub repository tqnonline/agent-forge (2 stars, last pushed 5mo ago), licensed BSD-3-Clause. It adds 162 tokens to every session and 2,560 once invoked, about $0.0006 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-31.
Other skills, from other repositories
aws-cost-cleanup
Automated cleanup of unused AWS resources to reduce costs.
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.
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…