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-123-budget-pacing-daily-allocation-scriptsgit 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-123-budget-pacing-daily-allocation-scripts)<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-123-budget-pacing-daily-allocation-scripts"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-123-budget-pacing-daily-allocation-scripts/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-123-budget-pacing-daily-allocation-scripts"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-123-budget-pacing-daily-allocation-scripts.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.00028 | $0.00604 |
| Opus 5.5 | $0.00011 | $0.00242 |
| Sonnet 5.5 | $0.00006 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
skill-123-budget-pacing-daily-allocation-scripts 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 21d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill 123: Budget Pacing and Daily Allocation
Purpose
Analyze day-of-week performance patterns to optimize daily budget allocation and ensure proper monthly budget pacing. This helps capture more conversions on high-efficiency days while avoiding under/overspend.
Data Requirements
Data Source: Custom GAQL Required
The standard export does not include day-of-week segmented data.
GAQL Query:
SELECT
campaign.name,
campaign.id,
segments.day_of_week,
metrics.impressions,
metrics.clicks,
metrics.cost_micros,
metrics.conversions,
metrics.conversions_value
FROM campaign
WHERE segments.date BETWEEN '{start_date}' AND '{end_date}'
AND campaign.status = 'ENABLED'
ORDER BY campaign.name, segments.day_of_week
Run via /google-ads:get-custom with query name day_of_week_performance.
Analysis Steps
- Fetch day-of-week data: Run custom GAQL query for 90 days of segmented data
- Calculate efficiency indices: Compare CPA/ROAS by day vs weekly average
- Identify patterns: Flag high-efficiency days (low CPA) and low-efficiency days (high CPA)
- Design allocation strategy: Create day-based budget multipliers
- Check monthly pacing: Compare spend-to-date vs budget-to-date
Thresholds
| Condition | Severity |
|---|---|
| Day CPA > 50% above average | Critical |
| Monthly underpacing > 20% | Warning |
| Monthly overpacing > 10% | Warning |
| Day efficiency variance > 30% | Info |
Output
Short format (default):
## Budget Pacing Audit
**Account:** [Name] | **Monthly Budget:** $[X] | **Pacing:** [On Track/Under/Over]
### Day-of-Week Efficiency
| Day | CPA | Efficiency | Recommended Multiplier |
|-----|-----|------------|----------------------|
| Monday | $[X] | +20% | 1.2x |
| Saturday | $[X] | -30% | 0.7x |
### Pacing Status
- Days remaining: [X]
- Budget remaining: $[X]
- Required daily: $[X] (current avg: $[Y])
### Recommendations
1. Increase [Day] budget by [X]% (best efficiency)
2. Reduce [Day] budget by [X]% (lowest efficiency)
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.
- 21d ago First seen · 82 lines · 28 tokens per session scan A a5262ded5e82
skill-123-budget-pacing-daily-allocation-scripts is a skill published in the GitHub repository TrueClicks/claude-plugins (2 stars, last pushed 22d ago), licensed MIT. It adds 28 tokens to every session and 604 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-10-08.
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…