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 agentmods add skills/themattberman/meta-ads-kit/budget-optimizernpx skills add TheMattBerman/meta-ads-kit --skill budget-optimizergit clone --depth 1 https://github.com/TheMattBerman/meta-ads-kitWrote 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/themattberman/meta-ads-kit/budget-optimizer)<a href="https://agentmods.dev/skills/themattberman/meta-ads-kit/budget-optimizer"><img src="https://agentmods.dev/badge/skills/themattberman/meta-ads-kit/budget-optimizer.svg" alt="Measured on agentmods" 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 | $0.00025 | $0.00433 |
| Opus 5 | $0.00013 | $0.00217 |
| Sonnet 5 | $0.00005 | $0.00087 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
budget-optimizer 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 5d 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.
What it actually says
Budget Optimizer — Put Money Where It Works
Most ad accounts have the same problem: budget spread evenly across campaigns when performance isn't even close to even. This skill finds where your money works hardest and recommends shifts.
Reports
Efficiency Analysis
Rank campaigns/adsets by cost efficiency (CPA, ROAS, or CPC depending on objectives).
Tell me: "Where's my money working best?"
Or: "Analyze spend efficiency"
Budget Shift Recommendations
Compare performance across campaigns, recommend moving budget from losers to winners.
Tell me: "How should I shift my budget?"
Or: "Optimize my ad spend"
Spend Pacing
Check if campaigns are on pace for their daily/lifetime budgets.
Tell me: "Am I overspending or underspending?"
Or: "Check spend pacing"
Scripts
# Efficiency ranking
./run.sh efficiency [--account act_123] [--preset last_7d]
# Spend pacing check
./run.sh pacing [--account act_123]
Invocation
- Pull campaign and adset level insights
- Calculate efficiency metrics (CPA, ROAS, CPC relative to spend)
- Compare against benchmarks in
ad-config.json - Identify top and bottom performers
- Calculate recommended budget shifts (% based)
- Present recommendations with clear reasoning
- Never adjust budget without explicit approval
- Log decisions to
workspace/brand/learnings.md
Safety
Budget changes are high-risk actions. This skill:
- Always shows current vs. recommended budget
- Explains the reasoning (data-backed)
- Waits for explicit "yes" before executing
- Logs every budget change for audit trail
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 79 lines · 25 tokens per session scan A d6829f669938
budget-optimizer is a skill published in the GitHub repository TheMattBerman/meta-ads-kit (311 stars, last pushed 2mo ago), licensed MIT. It adds 25 tokens to every session and 433 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…