What problem does it solve?
Cloud cost spikes often go unnoticed until the monthly invoice arrives. This Skill runs a daily, read-only sweep of AWS Cost Explorer data, maintains a per-service and per-account spend baseline, and alerts your team the day spend breaks out of its normal pattern — with a suspected driver attached.
Core Features & Use Cases
- Baseline-Based Detection: Builds a trailing ~30-day baseline per service/account pair and flags spend exceeding a configurable percentage threshold, rather than using flat dollar limits.
- Driver Attribution: Distinguishes new resources, traffic surges, region shifts, and price changes by comparing cost against usage quantities, so alerts are actionable.
- Persistent Memory Ledger: Stores baselines, anomaly history, and confirmed seasonal patterns in
.kortix/memory/cloud-cost-baseline.md, sharpening accuracy across daily runs.
- Use Case: A daily cron re-prompts one persistent session; when EC2 spend in one account jumps 62% above baseline, the team gets a Slack message showing the delta and evidence that usage (requests) rose proportionally — a traffic surge, not a new resource.
Quick Start
Ask the agent to run the daily cost-anomaly sweep and report any AWS spend that broke its baseline yesterday.