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.
git 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/agents/cletrics/finops-agents/finops-intersections-coordinator)<a href="https://agentmods.dev/agents/cletrics/finops-agents/finops-intersections-coordinator"><img src="https://agentmods.dev/badge/agents/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/agents/cletrics/finops-agents/finops-intersections-coordinator"><img src="https://agentmods.dev/badge/agents/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.00970 |
| Opus 5.5 | $0.00020 | $0.00388 |
| Sonnet 5.5 | $0.00010 | $0.00194 |
| 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 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 — 94 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.
- 1mo ago First seen · 94 lines · 51 tokens per session scan A 264e27c4283a
FinOps Intersections Coordinator is an agent published in the GitHub repository Cletrics/finops-agents (47 stars, last pushed 5mo ago), licensed MIT. It adds 51 tokens to every session and 970 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 agents, from other repositories
financial-manager
Budget planning, cost estimation, SOW creation, and financial tracking for automotive software projects.
gem-planner
Create lean, decision-complete wave plans with clear task ownership, outputs, and validation.
stock-balance-sheet-reviewer
Specialist for US-stock balance-sheet health review — leverage (Net Debt/EBITDA), liquidity (current ratio, cash runway), goodwill concentration and impairment history, working capital trends (DSO, inventory days), off-balance-sheet items (commitments, contingencies), and pension underfunding. Use when assessing…
task-orchestrator
Use this agent when you need to coordinate and manage the execution of Task Master tasks, especially when dealing with complex task dependencies and parallel execution opportunities. This agent should be invoked at the beginning of a work session to analyze the task queue, identify parallelizable work, and orchestrate…
requirements-analyst-beads
Requirements analyst that turns gaps, assumptions, constraints, and follow-up work into Beads-tracked items.
process-quality-measurement-analyst-aspice40
Measurement analyst specializing in ASPICE 4.0 MAN.6 process. Collects and analyzes measurement data to support project management and process improvement decisions.