Borrowing it
Nothing to install: this file belongs to Pauesome/Paid-Media-MCP. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Pauesome/Paid-Media-MCP/main/.claude/skills/ads-pacing-monitor/SKILL.mdgit clone --depth 1 https://github.com/Pauesome/Paid-Media-MCPWrote 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/pauesome/paid-media-mcp/ads-pacing-monitor)<a href="https://agentmods.dev/skills/pauesome/paid-media-mcp/ads-pacing-monitor"><img src="https://agentmods.dev/badge/skills/pauesome/paid-media-mcp/ads-pacing-monitor/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/pauesome/paid-media-mcp/ads-pacing-monitor"><img src="https://agentmods.dev/badge/skills/pauesome/paid-media-mcp/ads-pacing-monitor.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.00124 | $0.01461 |
| Opus 5 | $0.00062 | $0.00731 |
| Sonnet 5 | $0.00025 | $0.00292 |
| Haiku 4.5 | $0.00012 | $0.00146 |
Grade A, and why
ads-pacing-monitor 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ads Pacing Monitor — Spain
Answers the question: "At today's run rate, where do I land on month-end spend vs target?" Produces a per-account, per-campaign pacing status with specific daily-budget adjustments. Cron-friendly — ideal for Monday-morning and mid-week checks.
Required Inputs
client_id(required) — resolved vialist_clientsmonthly_targets(required) — map of account or campaign → monthly target in EUR. Can be per-platform total (e.g.{"google_ads": 5000, "meta_ads": 3000, "tiktok_ads": 1500}) or per-campaign (e.g.{"Brand — Exact": 1200, "Non-Brand": 2000}). Without this input the skill cannot compute pacing.as_of_date(optional) — the reference date for "today". Defaults to current date. Useas_of_dateto re-run a historical pacing view.
Fail fast if monthly_targets is missing. Generic pacing without a
target is meaningless.
Account Context (optional)
If you maintain notes for the account, factor in:
- Seasonality: weight the pacing projection if the account has a known seasonal spend curve (e.g. front-loaded December, back-loaded September). Plain linear pacing misleads in those cases.
- Pacing philosophy: some accounts want linear daily pacing (budget / days_in_month) and flag anything >5% off; others are fine with back-loaded pacing if the trajectory is trending toward target.
- Any frozen campaigns: a campaign paused for compliance review or creative refresh should not be flagged as under-pacing.
Without account notes, assume linear pacing + flag everything literally.
Data Collection (MCP Tools, parallel)
Pull MTD (start-of-month to as_of_date) for every configured platform:
get_google_ads_campaign_performance— ifgoogle_adsconfiguredget_meta_campaign_performance— ifmeta_adsconfiguredget_tiktok_campaign_performance— iftiktok_adsconfigured
Each call uses the same date range: [YYYY-MM-01, as_of_date].
Pacing Math
For each account / campaign:
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 · 139 lines · 124 tokens per session scan A 018afb6bec0f
ads-pacing-monitor is a skill published in the GitHub repository Pauesome/Paid-Media-MCP (1 stars, last pushed 2mo ago), licensed MIT. It adds 124 tokens to every session and 1,461 once invoked, about $0.0006 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…