/Catalogue/Prompt/hoangsonww/hoangsonww-claude-code-agent-monitor-daily-budget-check

Origin: github

daily-budget-check

Run a daily spend check-in against a daily budget on the Agent Monitor dashboard — today's spend vs the daily target, pace through the day, and the projected overage if the current pace holds. Uses /api/pricing/cost and /api/sessions (grouped by started_at = today). Use for a quick daily spend check-in or a morning/evening budget pulse.

by hoangsonww · updated 20h ago · imported from GitHub

Installs0+0/7d
Security score0/100
Retention 14d0%
GitHub stars1K

Skill logic

Execution graph
User message
Prompt rewrites behaviour
Response

SKILL.md

View on GitHub ↗

Daily Budget Check

A fast daily pulse: are you on pace against today's budget?

Input

The user provides: $ARGUMENTS

This is the daily budget in dollars — e.g. "5" or "$5/day". If omitted, ask for one or derive it from a monthly budget (monthly / days_in_month) and state the assumption.

Data Sources

EndpointReturns
GET /api/pricing/cost{ total_cost, breakdown: [{ model, input_tokens, output_tokens, cache_read_tokens, cache_write_tokens, cost, matched_rule }] } — fleet-wide spend and the avg cost-per-session used to value today's sessions
GET /api/sessions?limit=200Session list with inline cost and started_at — filter to today (DATE(started_at) = today) to isolate today's spend

Method

Spend has no per-day field, so isolate today from the session list:

  1. Today's sessions = sessions whose started_at is today (local date).
  2. Today's spend = sum of inline cost over today's sessions. If inline cost is absent for some rows, fall back to today_session_count × (total_cost / total_session_count) and flag it as approximate.
  3. Pace: fraction_of_day_elapsed = hours_since_midnight / 24. expected_by_now = daily_budget × fraction_of_day_elapsed.
  4. Pace delta = today_spend − expected_by_now (▲ ahead of budget / ▼ behind).
  5. End-of-day projection: projected_today = today_spend / fraction_of_day_elapsed (linear extrapolation of the current pace). Guard against tiny fraction_of_day_elapsed early in the day — if under ~0.1, label the projection low-confidence.
  6. Projected overage = projected_today − daily_budget (positive = over).

Report Sections

1. Today vs budget

One headline line: today's spend / daily budget, and the percent consumed. Verdict: under / on pace / over.

2. Pace

expected_by_now vs actual today_spend, the ▲/▼ pace delta, and the fraction of the day elapsed.

3. End-of-day projection

projected_today and the projected overage/headroom vs the daily budget. Note the confidence (low early in the day).

4. Today's drivers

Today's sessions ranked by cost (top 5): name/id, model, cost. Surface any premium-model session inflating the day.

5. Nudge

If projected over: one concrete cut (route the priciest session type cheaper — see model-savings; or arm a token_threshold rule via budget-set). If under: confirm headroom and the remaining daily allowance.

Output

Compact Markdown — this is a daily check-in, keep it tight. Currency as USD to 4 decimal places; pace deltas with ▲/▼. Lead with the verdict line.

Discussion

No comments yet — start the thread.

Sign in to join the discussion.

/More from hoangsonww/Claude-Code-Agent-Monitor

hoangsonww· 20h agoSandbox
config-audit

Prompts · TypeScript · v0.1.0

Run a full audit of the user's Claude Code configuration via the Agent Monitor Config Explorer API: counts per surface (user vs project), duplicate or overlapping skills and subagents, hooks that run shell commands, and which surfaces are read-only vs mutable. Reads /api/cc-config/overview, /skills, /agents, /commands, /hooks, and /settings. Use when reviewing your Claude Code setup for sprawl, duplication, or risk.

#ai-agents#claude-agents#claude-code

0 1K
hoangsonww· 20h agoSandbox
hook-inventory

Prompts · TypeScript · v0.1.0

Inventory hooks across the user, project, and project-local settings plus the ~/.claude/hooks scripts directory — read through the Agent Monitor Config Explorer API — and flag hooks that POST to the network or run arbitrary commands. Reads /api/cc-config/hooks and /api/cc-config/hook-scripts. Use when auditing hook safety.

#ai-agents#claude-agents#claude-code

0 1K
hoangsonww· 20h agoSandbox
mcp-audit

Prompts · TypeScript · v0.1.0

Audit the configured MCP servers (user + project scope) via the Agent Monitor Config Explorer API: transport (stdio vs http), command/args and env variable names, headers, and the source file each definition came from. Reads /api/cc-config/mcp. Use when reviewing MCP integrations for hygiene, duplication, or unexpected transports.

#ai-agents#claude-agents#claude-code

0 1K
hoangsonww· 20h agoSandbox
memory-review

Prompts · TypeScript · v0.1.0

Review the file-based memory store via the Agent Monitor Config Explorer API: the user and project CLAUDE.md plus per-project auto-memory files under ~/.claude/projects/<slug>/memory/*.md. Groups by project, shows the index (MEMORY.md) vs per-fact files, and flags stale or oversized facts. Reads /api/cc-config/memory and /api/cc-config/file?path=. Use when curating agent memory.

#ai-agents#claude-agents#claude-code

0 1K