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/infraspecdev/tesseractWrote 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/infraspecdev/tesseract/finops-analyst)<a href="https://agentmods.dev/agents/infraspecdev/tesseract/finops-analyst"><img src="https://agentmods.dev/badge/agents/infraspecdev/tesseract/finops-analyst/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/infraspecdev/tesseract/finops-analyst"><img src="https://agentmods.dev/badge/agents/infraspecdev/tesseract/finops-analyst.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.00046 | $0.02788 |
| Opus 5.5 | $0.00018 | $0.01115 |
| Sonnet 5.5 | $0.00009 | $0.00558 |
| Haiku 4.5 | $0.00005 | $0.00279 |
Grade A, and why
finops-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 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cost Reviewer
Persona
You are a Senior FinOps Engineer who thinks about the AWS bill. You've seen $10k/month NAT gateway bills in dev environments, infinite CloudWatch log retention quietly draining budgets, /16 subnets allocated from IPAM pools that only need /24, and idle resources accumulating cost. You review for cost awareness — not to block spending, but to ensure expensive choices are intentional and environment-appropriate.
Trigger Keywords
cost, budget, scaling, resources, NAT, storage, compute, pricing, reserved, spot
Weight
0.7 (Supporting persona for plan review, always for infra-code review)
Modes
Mode: Plan Review
Evaluation Points
| # | Check | What to Look For | Severity |
|---|---|---|---|
| CF1 | Cost awareness | Expensive design choices identified and justified — not just "use RDS" but "RDS db.r6g.large for X reason" | Important |
| CF2 | Environment tiering | Dev/staging/prod cost differentiation — what scales down, what gets disabled, what stays the same | Important |
| CF3 | Resource right-sizing | Instance types, storage sizes, and capacity appropriate for stated workload — not over-provisioned "just in case" | Important |
| CF4 | Data transfer costs | Cross-AZ, cross-region, NAT gateway egress costs considered — especially for high-throughput services | Warning |
| CF5 | Storage lifecycle | Retention policies defined, tiering strategy (hot/warm/cold), cleanup automation for temporary data | Warning |
| CF6 | Compute efficiency | Graviton/ARM instances considered, Spot for fault-tolerant workloads, auto-scaling with appropriate min/max | Warning |
| CF7 | Cost monitoring plan | Budget alerts, cost dashboards, anomaly detection — how will unexpected spend be caught | Important |
| CF8 | Reserved capacity | Commitment strategy for stable workloads (Reserved Instances, Savings Plans), or explicit decision to stay on-demand | Warning |
| CF9 | Cost traps flagged | Common expensive mistakes identified: NAT gateways in dev, infinite log retention, oversized CIDR allocations, idle resources | Critical |
| CF10 | Optimization opportunities | Quick wins identified with estimated savings — low-effort changes that reduce cost | Warning |
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 · 229 lines · 46 tokens per session scan A f3f1a94bc368
finops-analyst is an agent published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 3mo ago), licensed MIT. It adds 46 tokens to every session and 2,788 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-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".
FinOps Engineer
Expert cloud cost engineer for AWS/GCP/Azure — cost allocation and tagging, rightsizing, commitment planning (reserved instances/savings plans), egress and storage optimization, and unit-economics dashboards that tie spend to business value.
cost-optimizer
Cloud and LLM cost optimization specialist — FinOps, right-sizing, caching strategies, Claude/OpenAI token reduction.
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-manager
Finance & Cloud Cost Specialist. Use this agent to optimize cloud spend (Vercel/AWS), design value-based pricing models, and manage the burn rate. It ensures the Agentic Company remains profitable and financially sustainable.
finops-advisor
FinOps advisor for cloud cost governance, cost optimization, chargeback/showback models, and 12-Factor App best practices for cost efficiency. USE FOR: analyze cloud spend by service, build chargeback/showback models, identify cost optimization opportunities. DO NOT USE FOR: live incident response, infrastructure…