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-050-shared-budget-appropriateness-checkgit 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-050-shared-budget-appropriateness-check)<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-050-shared-budget-appropriateness-check"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-050-shared-budget-appropriateness-check/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-050-shared-budget-appropriateness-check"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-050-shared-budget-appropriateness-check.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.00027 | $0.00725 |
| Opus 5 | $0.00014 | $0.00362 |
| Sonnet 5 | $0.00005 | $0.00145 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
skill-050-shared-budget-appropriateness-check 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 12d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill 050: Shared Budget Appropriateness Check
Purpose
Shared budgets pool spend across campaigns, which can simplify management but also cause uneven distribution, campaign starvation, or difficulty in performance analysis. This skill evaluates whether shared budgets are appropriate for grouped campaigns and identifies spend distribution issues.
Data Requirements
Data Source: Standard
Standard Data:
data/account/budgets.md- Shared budgets and linked campaignsdata/account/campaigns/*/campaign.md- Budget settings, shared budget IDsdata/performance/campaigns/*/campaign_metrics_30_days.md- Campaign spend and conversions
Reference GAQL:
SELECT
campaign_budget.id,
campaign_budget.name,
campaign_budget.amount_micros,
campaign_budget.explicitly_shared,
campaign_budget.reference_count,
campaign.id,
campaign.name,
metrics.cost_micros,
metrics.conversions,
metrics.impressions
FROM campaign
WHERE campaign.status = 'ENABLED'
AND campaign_budget.explicitly_shared = TRUE
AND segments.date DURING LAST_30_DAYS
Use /google-ads:get-custom for shared budget reference counts.
Analysis Steps
-
Identify shared budgets: Find all shared budgets with budget ID, name, daily amount, number of campaigns, campaign names/types.
-
Analyze spend distribution: Calculate each campaign's share of spend, identify dominant campaigns (>50%), identify starved campaigns (<10%), calculate concentration index.
-
Assess campaign compatibility: Same business objective? Similar CPA/ROAS? Complementary or competing? Different priority levels?
-
Evaluate performance impact: Are efficient campaigns constrained? Are inefficient campaigns getting too much share?
-
Calculate separation impact: Model individual budgets based on current performance, project impact on conversions.
Thresholds
| Condition | Severity |
|---|---|
| Shared budget with different goals | Critical |
| Single campaign >60% of shared spend | High |
| Campaign <5% of shared spend | High |
| CPA range within shared >50% | Warning |
| >5 campaigns sharing budget | Warning |
| Concentration index (HHI) >0.40 | Warning |
| 2-3 campaigns evenly shared | Info |
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.
- 12d ago First seen · 90 lines · 27 tokens per session scan A bf546ec9088d
skill-050-shared-budget-appropriateness-check is a skill published in the GitHub repository TrueClicks/claude-plugins (2 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 725 once invoked, about $0.0001 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…