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 mathiaschu/meta-ads-analyzer --skill skillgit clone --depth 1 https://github.com/mathiaschu/meta-ads-analyzerWrote 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/mathiaschu/meta-ads-analyzer/skill)<a href="https://agentmods.dev/skills/mathiaschu/meta-ads-analyzer/skill"><img src="https://agentmods.dev/badge/skills/mathiaschu/meta-ads-analyzer/skill/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/mathiaschu/meta-ads-analyzer/skill"><img src="https://agentmods.dev/badge/skills/mathiaschu/meta-ads-analyzer/skill.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.00082 | $0.01730 |
| Opus 5.5 | $0.00033 | $0.00692 |
| Sonnet 5.5 | $0.00016 | $0.00346 |
| Haiku 4.5 | $0.00008 | $0.00173 |
Grade A, and why
meta-ads-analyzer 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meta Ads Analysis & Diagnosis Skill
When to Use This Skill
Use this skill when you need to analyze and diagnose Meta Ads campaign performance, including:
- Interpreting campaign, ad set, or ad-level performance data
- Identifying root causes of performance issues
- Generating actionable optimization recommendations
- Understanding why Meta's system makes certain budget allocation decisions
- Analyzing CSV exports, screenshots, or raw data from Meta Ads Manager
Result Recommendations (MANDATORY for Final Reports)
IMPORTANT: The following rules are MANDATORY and MUST be strictly followed when writing the final analysis report. These are not optional guidelines — they define the required standards for all deliverables.
- NEVER recommend pausing or reducing budget for any segment based solely on higher average CPA/CPM in breakdown reports. Higher average cost does NOT mean poor performance — it often reflects the system capturing low marginal cost opportunities earlier. Removing segments may increase overall costs. Always frame changes as testable hypotheses, not directives.
- ALWAYS justify recommendations with data evidence, Meta's system mechanics, and expected impact on overall campaign performance.
- EVERY insight must include data evidence and explanation. Every recommendation must be actionable and verifiable.
- ALIGN WITH OFFICIAL RECOMMENDATIONS. Check
get_recommendationsAPI first. If diverging, explicitly acknowledge and explain why. - Disambiguate clicks. Never use the term "clicks" alone. Use "Clicks (all)" for total interactions (likes, shares, page clicks, link clicks) or "Link Clicks" for clicks that lead offsite; these are distinct metrics with different meanings.
- Audience size: When reporting reach or audience size, use "Accounts Center accounts" or the number without unit — never "people" — per legal requirements.
Metric Naming Guidelines
IMPORTANT: Always rename metric names to standardized, non-sensitive names exactly as specified below in all responses:
What ships with it
9 files 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.
- references/ad_auctions.md 1004 B
- references/ad_relevance_diagnostics.md 1.4 KB
- references/auction_overlap.md 904 B
- references/bid_strategies.md 855 B
- references/breakdown_effect.md 1.6 KB
- references/core_concepts.md 2.0 KB
- references/learning_phase.md 1.1 KB
- references/pacing.md 984 B
- references/performance_fluctuations.md 1.3 KB
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 · 135 lines · 82 tokens per session scan A 6b66f3f6b367
meta-ads-analyzer is a skill published in the GitHub repository mathiaschu/meta-ads-analyzer (452 stars, last pushed 7mo ago), licensed MIT. It adds 82 tokens to every session and 1,730 once invoked, about $0.0003 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-30.
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…