Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add TrueClicks/claude-plugins --skill skill-049-budget-overspend-underspend-alert-configurationgit clone --depth 1 https://github.com/TrueClicks/claude-pluginsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/trueclicks/claude-plugins/skill-049-budget-overspend-underspend-alert-configuration)<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-049-budget-overspend-underspend-alert-configuration"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-049-budget-overspend-underspend-alert-configuration/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-049-budget-overspend-underspend-alert-configuration"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-049-budget-overspend-underspend-alert-configuration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00029 | $0.00737 |
| Opus 5.5 | $0.00012 | $0.00295 |
| Sonnet 5.5 | $0.00006 | $0.00147 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade A, and why
skill-049-budget-overspend-underspend-alert-configuration scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill 049: Budget Overspend/Underspend Alert Configuration
Purpose
Budget pacing issues often go unnoticed until month-end. This skill defines alert thresholds, identifies campaigns currently triggering alerts, and recommends automated monitoring rules for daily budget overspend, monthly pacing variance, and sudden spend changes.
Data Requirements
Data Source: Custom GAQL Required
The standard export provides aggregated data but not daily spend patterns needed for alert detection.
Standard Data:
data/account/campaigns/*/campaign.md- Budget settingsdata/performance/campaigns/*/campaign_metrics_30_days.md- Total spend (baseline)
GAQL Query:
SELECT
campaign.id,
campaign.name,
campaign_budget.amount_micros,
metrics.cost_micros,
segments.date
FROM campaign
WHERE campaign.status = 'ENABLED'
AND segments.date DURING LAST_14_DAYS
ORDER BY segments.date DESC
Run via /google-ads:get-custom with query name budget_alerts.
Analysis Steps
-
Define alert thresholds: Daily overspend (Warning >110%, Alert >150%, Critical >200%), Monthly pacing (Under <85%, Over >115%), Sudden change (+/-30% day-over-day).
-
Calculate current alert status: Daily budget utilization, month-to-date pacing, 7-day trend, day-over-day change.
-
Identify triggered alerts: List campaigns currently triggering alerts with severity, duration, and trend.
-
Prioritize alerts: Rank by financial impact, severity level, duration, client sensitivity.
-
Configure monitoring rules: Recommend automated rules for scripts, Google Ads rules, or third-party tools.
Thresholds
| Condition | Severity |
|---|---|
| Daily spend >200% budget | Critical |
| Multiple campaigns alerting simultaneously | Critical |
| Monthly pacing >130% or <70% | High |
| Day-over-day change >50% | High |
| Alert active >7 days | High |
| Monthly pacing 110-130% or 70-85% | Warning |
| Daily spend 150-200% budget | Warning |
| Day-over-day change 30-50% | Warning |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 87 lines · 29 tokens per session scan A 7e80630a278e
skill-049-budget-overspend-underspend-alert-configuration is a skill published in the GitHub repository TrueClicks/claude-plugins (2 stars, last pushed 22d ago), licensed MIT. It adds 29 tokens to every session and 737 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…