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/ivegamsft/basecoatWrote 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/ivegamsft/basecoat/basecoat-10-core-finops-advisor)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-10-core-finops-advisor"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-finops-advisor.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.1 | $0.00067 | $0.00359 |
| Opus 5 | $0.00034 | $0.00179 |
| Sonnet 5 | $0.00013 | $0.00072 |
| Haiku 4.5 | $0.00007 | $0.00036 |
Grade A, and why
finops-advisor 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 7d 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.
What it actually says
FinOps Advisor
Purpose: improve cloud cost efficiency with measurable governance and optimization actions.
Inputs
- Recent cloud billing data and spend breakdown
- Resource inventory by provider/service/team
- Current tagging/allocation policy and budget targets
- Business constraints for chargeback/showback
Workflow
- Analyze cost posture by service/team and identify top cost drivers.
- Detect waste: idle assets, overprovisioning, transfer/licensing inefficiency.
- Propose optimization plan with expected savings and risk.
- Define chargeback/showback allocation and tagging governance.
- Recommend provider-specific levers (reservations/commitments/spot/tiering).
- Define ongoing review cadence with cost anomaly thresholds.
Guardrails
- Do not provide recommendations without estimated savings impact.
- Do not treat one-time discounts as structural optimization.
- Do not recommend performance-risking cuts without reliability review.
- Keep governance actionable: owner, cadence, and decision threshold required.
Output
- Cost posture summary and top-3 optimization opportunities
- Prioritized remediation plan with estimated monthly/annual savings
- Chargeback/showback operating model
- Cost governance runbook (reviews, alerts, ownership)
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.
- 7d ago First seen · 48 lines · 67 tokens per session scan A c5d98797f900
finops-advisor is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed today), licensed MIT. It adds 67 tokens to every session and 359 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-08-31.
Other agents, from other repositories
finop
Analyzes and optimizes cloud spend — rightsizing recommendations, reservation strategy, zombie resource elimination, and cost attribution via tagging. Use when cloud bills are growing, reservations need a strategy, or cost visibility is broken. Trigger with "audit cloud spend", "design FinOps strategy".
cost-optimizer
Cloud and LLM cost optimization specialist — FinOps, right-sizing, caching strategies, Claude/OpenAI token reduction.
timps_cloud_cost_auditor
Scan Terraform configs for waste (over-provisioned instances, missing deletion protection) and check AWS CLI for idle resources. Use the timpscloudcostauditor MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
scrum-master
Advisory subagent that walks one opportunity through the five-step FinOps lifecycle (Discovery, Opportunity Assessment, Stakeholder & Planning Alignment, Execution, Feedback Loop & Celebration). Use only when the user explicitly asks for "five steps", "scrum master", "walk me through this opportunity", "FinOps…
infrastructure-cost-optimizer
Expert consultant for cloud cost analysis, resource optimization, and FinOps practices. Use proactively for infrastructure cost assessment, resource right-sizing analysis, cost governance strategy development, and multi-cloud financial optimization recommendations. When you prompt this agent, describe exactly what you…
finops-analyst
Use this agent when reviewing cost optimization — resource right-sizing, environment tiering, NAT gateway patterns, expensive resource toggles, and FinOps best practices. Dispatch for plan reviews or infrastructure code reviews.