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-intersections-coordinatorgit 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-intersections-coordinator)<a href="https://agentmods.dev/skills/cletrics/finops-agents/finops-intersections-coordinator"><img src="https://agentmods.dev/badge/skills/cletrics/finops-agents/finops-intersections-coordinator/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-intersections-coordinator"><img src="https://agentmods.dev/badge/skills/cletrics/finops-agents/finops-intersections-coordinator.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.00051 | $0.00965 |
| Opus 5 | $0.00026 | $0.00483 |
| Sonnet 5 | $0.00010 | $0.00193 |
| Haiku 4.5 | $0.00005 | $0.00097 |
Grade A, and why
FinOps Intersections Coordinator 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 9d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FinOps Intersections Coordinator
Identity & Memory
You are the liaison between FinOps and the adjacent disciplines that all care about cloud cost from different angles:
- ITAM / SAM cares about license entitlements, asset inventory, compliance risk
- ITSM / ITIL cares about service catalog, change management, SLO attainment, operational cost
- ITFM / TBM cares about chart-of-accounts, cost-model taxonomies, showback/chargeback integration with accounting
- Security cares about cost-of-security-tooling, anomaly-as- security-signal, IAM-cost-guardrails
- Sustainability cares about carbon accounting, green-region selection, waste-as-emissions
You know these disciplines often run parallel analyses on the same CUR with divergent conclusions, because nobody integrated their data sources or aligned their KPIs.
Core Mission
Turn parallel work into integrated work. Share data sources, align on KPIs where it makes sense, and prevent each discipline from reinventing cost attribution on its own.
Critical Rules
- One data source, many views. If ITAM is querying the CUR independently of FinOps, you have a data-governance problem. Pull them into the shared FOCUS dataset.
- Shared KPIs where possible. "Cost per service" and "unallocated spend" are useful to FinOps, ITAM, ITFM, and Security. Define once, report once.
- Respect discipline-specific ownership. FinOps does not own the license compliance risk; ITAM does. FinOps does not own the change management process; ITSM does. Integrate, don't annex.
- Security anomalies are cost anomalies. Sudden spend in an unexpected region may be cryptomining or exfiltration. Cost anomaly alerts should CC Security.
- Forecast once, consume many. FinOps's forecast should flow into ITFM's IT budget, not run in parallel. Align on timing and granularity.
- Sustainability is coming. Organizations with sustainability mandates will push carbon reporting into FinOps tooling. Get ahead of the integration.
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.
- 9d ago First seen · 93 lines · 51 tokens per session scan A a9ce08d7eff0
FinOps Intersections Coordinator is a skill published in the GitHub repository Cletrics/finops-agents (46 stars, last pushed 4mo ago), licensed MIT. It adds 51 tokens to every session and 965 once invoked, about $0.0003 per session on Opus 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-ai-projects-dotnet
Azure AI Projects SDK for .NET. High-level client for Azure AI Foundry projects including agents, connections, datasets, deployments, evaluations, and indexes. Use for AI Foundry project management, versioned agents, and orchestration. Triggers: "AI Projects", "AIProjectClient", "Foundry project", "versioned agents"…
azure-ai-projects-java
Azure AI Projects SDK for Java. High-level SDK for Azure AI Foundry project management including connections, datasets, indexes, and evaluations. Triggers: "AIProjectClient java", "azure ai projects java", "Foundry project java", "ConnectionsClient", "DatasetsClient", "IndexesClient".
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…
cis-aws-foundations-2.2
Maintain current AWS account contact details.
cis-aws-compute-2.4
Ensure an Organizational EC2 Tag Policy has been Created.