cost-alert
Review the configured cost alert rules and the alerts currently fired on the Agent Monitor dashboard, then explain exactly what tripped and why. Uses /api/alerts (fired feed) and /api/alerts/rules (definitions). Use when checking spend alerts or asking why a cost alarm went off.
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill cost-alert --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Cost Alert Audit the spend guardrails: which rules exist, which have fired, and what tripped them. ## Input The user provides: **$ARGUMENTS** This may be empty (review everything), `"unacked"` (only unacknowledged alerts), or a rule name to focus on. ## Data Sources | Endpoint | Returns | |----------|---------| | `GET /api/alerts/rules` | `{ rules: [{ id, name, rule_type, config, enabled, cooldown_seconds }] }` — the guardrail definitions | | `GET /api/alerts` | `{ alerts: [{ id, rule_id, rule_name, rule_type, session_id, agent_id, message, details, triggered_at, acked }], total, unacked, limit, offset }` — the fired-alert feed, newest first. `?unacked=true` filters to unacknowledged | ## What the rule types mean | `rule_type` | `config` | Fires when | |-------------|----------|------------| | `token_threshold` | `{ total_tokens }` | A session's cumulative tokens (input + output + cache_read + cache_write) cross the ceiling — the spend-relevant guardrail | | `event_pattern` | `{ event_type?, tool_name?, summary_contains?, count?, window_minutes? }` | Matching events reach `count` within the window | | `inactivity` | `{ minutes }` | An active session goes quiet for `minutes` | | `
- Input
- Data Sources
- What the rule types mean
- Report Sections
- 1. Configured guardrails
- 2. Fired alerts
- 3. What tripped — per alert
- 4. Next steps
- Output
What does the cost-alert skill do?
Review the configured cost alert rules and the alerts currently fired on the Agent Monitor dashboard, then explain exactly what tripped and why. Uses /api/alerts (fired feed) and /api/alerts/rules (definitions). Use when checking spend alerts or asking why a cost alarm went off.
How do I install it?
Run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill cost-alert --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From hoangsonww/Claude-Code-Agent-Monitor, a repository with 869 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.