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 skills add Cletrics/finops-agents --skill cross-az-egress-investigatorgit 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/skills/cletrics/finops-agents/cross-az-egress-investigator)<a href="https://agentmods.dev/skills/cletrics/finops-agents/cross-az-egress-investigator"><img src="https://agentmods.dev/badge/skills/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/skills/cletrics/finops-agents/cross-az-egress-investigator"><img src="https://agentmods.dev/badge/skills/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.00890 |
| Opus 5.5 | $0.00015 | $0.00356 |
| Sonnet 5.5 | $0.00008 | $0.00178 |
| 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 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 — 89 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.
- 1mo ago First seen · 89 lines · 38 tokens per session scan A c6aa032e2374
Cross-AZ Egress Investigator is a skill published in the GitHub repository Cletrics/finops-agents (47 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 890 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 skills, from other repositories
azure-compute
Azure VM/VMSS router. WHEN: create / provision / deploy / spin-up VM, recommend VM size, compare VM pricing, VMSS, scale set, autoscale, burstable, lightweight server, website, backend, GPU, machine learning, HPC simulation, dev/test, workload, family, load balancer, Flexible orchestration, Uniform orchestration, cost…
azure-cost
Azure cost management: query costs, forecast spending, optimize to reduce waste. WHEN: "Azure costs", "Azure bill", "cost breakdown", "how much am I spending", "forecast spending", "optimize costs", "reduce spending", "orphaned resources", "rightsize VMs", "cost spike", "reduce storage costs", "AKS cost". DO NOT USE…
cost-estimation
Forecast Azure spend and price planned resources or workloads. WHEN: "forecast Azure spending", "project next month cost", "compare forecast to my planning target", "how much will Azure cost", "estimate VM cost", "compare storage tiers", "compare Azure regions", "retail price", "EA rate card", "negotiated pricesheet".…
cost-governance
Govern Azure costs with budgets, alerts, tags, and policy restrictions. WHEN: "Azure budget health", "configured budget overrun", "list Azure budgets", "create Azure budget", "budget alerts", "budget coverage", "missing CostCenter tags", "allowed VM SKUs", "allowed Azure regions", "would this SKU be denied", "cost…
cost-optimization
Optimize existing Azure resources and analyze Reservations or Savings Plans. WHEN: "optimize Azure costs", "reduce cloud spending", "rightsize resources", "find idle resources", "orphaned disk", "deleted VM still charged", "public IP still charging", "reservation utilization", "Savings Plan coverage", "commitment…
cis-aws-foundations-2.2
Maintain current AWS account contact details.