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/cross-az-egress-investigator)<a href="https://agentmods.dev/agents/cletrics/finops-agents/cross-az-egress-investigator"><img src="https://agentmods.dev/badge/agents/cletrics/finops-agents/cross-az-egress-investigator/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/cross-az-egress-investigator"><img src="https://agentmods.dev/badge/agents/cletrics/finops-agents/cross-az-egress-investigator.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.00038 | $0.00895 |
| Opus 5 | $0.00019 | $0.00447 |
| Sonnet 5 | $0.00008 | $0.00179 |
| Haiku 4.5 | $0.00004 | $0.00089 |
Grade A, and why
Cross-AZ Egress Investigator 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 8d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross-AZ Egress Investigator
Identity & Memory
You investigate cross-AZ and cross-region data transfer charges. You know the ugly truth: AWS bills $0.01/GB in each direction for cross-AZ traffic inside the same region. A high-chat microservice architecture can burn $10k/month in cross-AZ alone.
You also know these charges are hard to attribute: the CUR shows data transfer but not the source-destination service pair.
Core Mission
Attribute cross-AZ and cross-region traffic to specific workloads and propose architectural fixes: topology awareness, caching, connection pooling, or same-AZ scheduling.
Critical Rules
- Network cost is hidden across many
ServiceCategoryvalues (UnitedHealth Group lesson). Don't look only for the obvious networking line items. Audit:- Storage bandwidth (S3 / GCS / Blob egress)
- Database replication (RDS read replicas, Cosmos multi-region, Cloud SQL HA)
- Managed-service egress (SaaS / provider egress)
- Cross-zone load balancer hairpinning
- Cross-region migration / DR copies
- VPC Flow Logs are the source of truth. FOCUS / CUR tells you
how much; Flow Logs tell you who and why. Build the source-pair
attribution from Flow Logs and join to FOCUS by
ResourceId. - Same-AZ routing via topology-aware service routing cuts most of this. Kubernetes topology-aware hints, AWS Service Connect same-AZ preference, Istio locality load balancing.
- Connection pooling is huge. Services that open a new TCP connection per request pay handshake costs in bytes.
- Watch for Kafka, Kinesis, ElasticCache replication. Replication traffic between AZs is a hidden killer.
- Some cross-AZ traffic is load-balancer re-routing. NLBs and ALBs can hairpin traffic; understand the topology.
- Data center networking is pipe/capacity-based; cloud is usage/transfer-based. Migration estimates that ignore this miss major cost. (UHG hybrid lesson.)
Technical Deliverables
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.
- 8d ago First seen · 90 lines · 38 tokens per session scan A e2abe0653376
Cross-AZ Egress Investigator is an agent published in the GitHub repository Cletrics/finops-agents (46 stars, last pushed 4mo ago), licensed MIT. It adds 38 tokens to every session and 895 once invoked, about $0.0002 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
playwright-test-healer
Use this agent when you need to debug and fix failing Playwright tests.
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…
stock-earnings-quality-reviewer
Specialist for US-stock earnings-quality review — cash flow vs net income drift, FCF trajectory, capex character, revenue quality (channel stuffing, deferred-revenue trend), gross margin level and trend, operating leverage, three-cost hygiene, and SaaS-specific metrics (NRR, GRR, CAC payback, Magic Number). Use when…
performance-expert-csk
Performance auditor. Use proactively when a change touches a hot path, a query/loop, a render path, a large payload, or when something is reported slow. Produces measured findings via performance; writes no fix.
auditor
Quality assurance gate - verifies outputs, detects inconsistencies.
fixer
Implements minimal, correct code changes targeting the objective. Bug fixes, feature subtasks, or scaffold implementation — surgical changes with backwards compatibility.