Agent skill · Data & Analytics

budget-set

Define a spend budget for Claude Code and, optionally, create a cost alert rule that fires when usage crosses the limit, via POST /api/alerts/rules on the Agent Monitor dashboard. Reads current spend from /api/pricing/cost to size the budget sensibly and explains every rule field before writing. Use when setting a spend limit or wiring up a budget guardrail.

hoangsonwwgithub.com/hoangsonwwGitHub ↗
claude-codeMIT
Install
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill budget-set --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: plugins/ccam-cost-guard/skills/budget-set/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 869
Language: TypeScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Budget Set Help the user define a spend budget and turn it into a live cost guardrail on the Agent Monitor dashboard. ## Input The user provides: **$ARGUMENTS** This is the budget to set — e.g. `"$50/month"`, `"$10/week"`, or `"200000 tokens"`. If a period is omitted, treat it as a monthly budget and say so. If no number is given, read current spend first and propose a target. ## Data Sources | Endpoint | Returns | |----------|---------| | `GET /api/pricing/cost` | `{ total_cost, breakdown: [{ model, input_tokens, output_tokens, cache_read_tokens, cache_write_tokens, cost, matched_rule }] }` — current spend, used to size the budget and compute the blended $/token rate | | `GET /api/alerts/rules` | `{ rules: [{ id, name, rule_type, config, enabled, cooldown_seconds }] }` — existing rules, so you don't create a duplicate guardrail | | `POST /api/alerts/rules` | Create a rule. Body: `{ name, rule_type, config, enabled?, cooldown_seconds? }`. Returns `{ rule }` | ## How a budget becomes a rule The dashboard's alerting engine fires on **tokens**, not dollars. The spend-relevant rule type is **`token_threshold`**, whose config is `{ total_tokens }` — it fires when a session's cumulativ

What's inside
Steps it walks through
  1. Input
  2. Data Sources
  3. How a budget becomes a rule
  4. Rule fields explained
  5. Report Sections
  6. 1. Current spend snapshot
  7. 2. Budget interpretation
  8. 3. Existing guardrails
  9. 4. Proposed alert rule
  10. 5. Confirmation
  11. Output
More from Claude-Code-Agent-Monitor
All skills →
About this skill
What does the budget-set skill do?

Define a spend budget for Claude Code and, optionally, create a cost alert rule that fires when usage crosses the limit, via POST /api/alerts/rules on the Agent Monitor dashboard. Reads current spend from /api/pricing/cost to size the budget sensibly and explains every rule field before writing. Use when setting a spend limit or wiring up a budget guardrail.

How do I install it?

Run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill budget-set --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.

Keep going