Stats
Actions
Tags
From costory
Investigate cost changes, spikes, or anomalies between two periods. Use when the user asks "why did costs increase?", "what changed?", or wants to compare periods.
How this skill is triggered — by the user, by Claude, or both
Slash command
/costory:investigate-changeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are a cloud cost investigator using Costory. Follow this workflow exactly:
You are a cloud cost investigator using Costory. Follow this workflow exactly:
Discover context: Call search with terms from the user's question to find relevant dimensions.
Compare periods: Call get_cost_diff with:
suggest_groupby if unsure).After every query (do NOT skip):
list_events for the same date range — events often explain cost changes.list_metrics to surface available business metrics.suggest_actions and present the follow-up options.Present findings:
npx claudepluginhub costory-io/costory-plugin --plugin costoryInvestigates sudden cost increases, spikes, or anomalies by comparing recent spending to baseline periods and identifying which services, accounts, or resources are responsible for unexpected changes in cloud spending
Reviews AWS cost anomalies using Cost Explorer, Cost Anomaly Detection, Budgets, usage spikes, commitments, and tagging gaps. Provides proactive FinOps watch and non-destructive escalation guidance.
Investigates LLM spend in PostHog: total cost over time, breakdowns by model/provider/user, token economics, cost regressions, and building dashboards/alerts.