From costory
Create a cost alert that monitors a query and notifies via Slack when thresholds are exceeded. Use when the user wants to be alerted about cost changes.
How this skill is triggered — by the user, by Claude, or both
Slash command
/costory:setup-alertThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are setting up a cost alert in Costory. Follow this workflow:
You are setting up a cost alert in Costory. Follow this workflow:
Understand what to monitor: Ask the user what they want to alert on if not clear (e.g. "Alert me if EC2 costs exceed $10k/month").
Create a saved view first: Call create_saved_view with the query configuration (groupBy, filters, date range) that captures what to monitor. Note the returned savedViewId.
Find Slack channels: Call list_slack_channels to discover available channels for notifications.
Create the alert: Call create_alert with:
savedViewId from step 2.Present the result: Include the alert URL so the user can view and edit it in the Costory UI.
npx claudepluginhub costory-io/costory-plugin --plugin costoryDetects Alibaba Cloud cost anomalies (MaxCompute, ECS spot, CDN, OSS) and coordinates response via budget alerts, DingTalk notifications, and remediation playbooks.
Creates alerting rules for Prometheus, Grafana, and PagerDuty with thresholds, routing, escalation, and runbooks. Useful for performance monitoring setup and refinement.
Aggregates agent-specific AWS costs via Cost Explorer and Pricing MCPs, issues budget alerts at thresholds, recommends Claude model downgrades by usage patterns, and vetoes deployments exceeding monthly ceilings.