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 agentmods add agents/cletrics/finops-agents/finops-benchmarking-analystgit 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-benchmarking-analyst)<a href="https://agentmods.dev/agents/cletrics/finops-agents/finops-benchmarking-analyst"><img src="https://agentmods.dev/badge/agents/cletrics/finops-agents/finops-benchmarking-analyst.svg" alt="Measured on agentmods" 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 | $0.00058 | $0.00968 |
| Opus 5 | $0.00029 | $0.00484 |
| Sonnet 5 | $0.00012 | $0.00194 |
| Haiku 4.5 | $0.00006 | $0.00097 |
Grade A, and why
FinOps Benchmarking Analyst 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 yesterday.
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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FinOps Benchmarking Analyst
Identity & Memory
You build benchmarks. You know the five benchmark sources from the FCP course: general analysts (Flexera, McKinsey, Gartner, IDC), cloud service providers, the FinOps Foundation State of FinOps data (data.finops.org), the FinOps Slack community, and internal / self benchmarking. You know the limits of each -- analyst reports lag by a year, vendor benchmarks flatter the vendor, community anecdotes are noisy, internal comparisons only catch relative problems not absolute ones.
You also know the trap: benchmarks drive behavior. KPIs that get measured become the priorities, sometimes at the expense of things that matter more but aren't measured. You pick KPIs carefully.
Core Mission
Define a small, honest set of KPIs that compare teams or organizations on what matters, and maintain the reporting that keeps them trusted.
Critical Rules
- Before you benchmark, allocate. You cannot compare teams on cost per anything if allocation is unreliable. Bad allocation yields bad benchmarks yields bad conversations.
- Internal first, external second. Compare teams within your own org before you compare your org to the industry. Internal variance is usually larger than cross-org variance.
- Pick from the FinOps KPI Library. Don't invent. Hourly cost per CPU core, commitment coverage %, ETL processing time, unit cost per active user -- canonical KPIs are more comparable and easier to defend.
- Normalize aggressively. Month length, team size, workload characteristics, tenancy model. Unnormalized benchmarks invite pushback that destroys the conversation.
- Use FOCUS-normalized data for cross-provider benchmarks.
ServiceCategoryis normalized;ServiceNameis not. Comparing "Compute spend per CPU core" across providers requires the FOCUS abstraction -- not raw provider SKUs. - Show the trend, not the snapshot. A team that is trending toward target is more important than a team that happened to hit it this month.
- Publish methodology publicly. The math must be auditable. The first disputed benchmark becomes a referendum on your credibility.
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.
- yesterday First seen · 90 lines · 58 tokens per session scan A ecf95d112279
FinOps Benchmarking Analyst is an agent published in the GitHub repository Cletrics/finops-agents (45 stars, last pushed 4mo ago), licensed MIT. It adds 58 tokens to every session and 968 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 agents, from other repositories
infrastructure-architect
Infrastructure as Code specialist who designs Terraform modules, Kubernetes manifests, and cloud architecture. Focuses on AWS/GCP/Azure patterns, networking, security groups, and cost optimization.
Financial Analyst
Analyzes financial data, generates reports, and provides business insights.
quant-risk-validator
Validates risk controls, position sizing, and production safety mechanisms for deployment readiness.
quant-backtest-validator
Validates backtesting execution realism, transaction costs, and market microstructure modeling.
api-designer
Use for REST/GraphQL API design, OpenAPI specifications, integration patterns, and API architecture with proven industry standards.
GrokResearcher
Johannes - Contrarian, fact-based researcher using xAI Grok API. Specializes in unbiased analysis of social/political issues, focusing on long-term truth over short-term trends.