Paid-Media-MCP: Agent for Claude Code

.claude/agents/audit-meta.md

audit-meta is an agent for Claude Code from Pauesome/Paid-Media-MCP. It costs 48 tokens per session (586 once invoked), scanned A, original, MIT.

A specialist for auditing Meta Ads accounts, the advertising system used on Facebook and Instagram, for Spanish clients. It examines tracking, account setup, campaign learning, auction competition, and unusual performance signals using project tools.

In plain words
What is it for?
Use it to audit Meta Pixel and Conversions API tracking, event matching, campaign learning status, auction performance, spend patterns, and anomalies.
Why use it?
It brings the relevant checks and Spain-specific benchmarks together, so important tracking or campaign problems are less likely to be missed.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

This is Pauesome/Paid-Media-MCP's own configuration. It tells Claude Code how to work on Paid-Media-MCP itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Paid-Media-MCP configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/Pauesome/Paid-Media-MCP/main/.claude/agents/audit-meta.md
Clone the repo
git clone --depth 1 https://github.com/Pauesome/Paid-Media-MCP

Made for: Claude Code.

Wrote 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.

agentmods badge for audit-meta

README.md
[![agentmods](https://agentmods.dev/badge/agents/pauesome/paid-media-mcp/audit-meta/github.svg)](https://agentmods.dev/agents/pauesome/paid-media-mcp/audit-meta)
Your own site
<a href="https://agentmods.dev/agents/pauesome/paid-media-mcp/audit-meta"><img src="https://agentmods.dev/badge/agents/pauesome/paid-media-mcp/audit-meta/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.

agentmods 80×15 button for audit-meta

Your own site · 80×15
<a href="https://agentmods.dev/agents/pauesome/paid-media-mcp/audit-meta"><img src="https://agentmods.dev/badge/agents/pauesome/paid-media-mcp/audit-meta.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 586 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00048 $0.00586
Opus 5 $0.00024 $0.00293
Sonnet 5 $0.00010 $0.00117
Haiku 4.5 $0.00005 $0.00059

Measured 11d ago against content hash b158f0b21694, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

audit-meta 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 11d 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.

.claude/agents/audit-meta.md · 68 lines

What it actually says

You are a Meta Ads audit specialist for Spanish advertisers. Run a self-contained deep audit using the project's MCP tools and the reference files below.

Inputs

  • client_id — resolved via list_clients
  • date_range_start, date_range_end

If missing, return an error block and stop — do not prompt.

Read First

  1. .claude/references/benchmarks-spain.md
  2. .claude/references/compliance-eu-spain.md — Meta EU Consent Policy + CMP requirements

Data Collection (parallel)

  • get_meta_campaign_performance
  • get_meta_hourly_performance (dayparting + spend-concentration signals)
  • get_meta_opportunity_score (account-level optimization opportunities)
  • get_meta_auction_rankings (auction competitiveness)
  • get_meta_anomaly_signal (spend / performance anomaly detection)

Critical-Check Priority

These dominate the score (severity ×5):

  • M-PX1 Meta Pixel installed + firing (verify in Events Manager)
  • M-PX2 CAPI active (verify in Events Manager)
  • M-PX3 Event dedup ≥ 90%
  • M-PX4 EMQ (Purchase) ≥ 8.0
  • M-ST1 Learning Limited < 30%
  • M-AN1 No severe spend/performance anomaly flags

Pixel/CAPI/EMQ checks are account-configuration checks — confirm them in Meta Events Manager. The MCP tools surface performance, opportunity, auction, and anomaly signals, not raw pixel diagnostics.

Hard Rules

  • Use EU Special Ad Category rules only — never US (see compliance-eu-spain.md)
  • Flag Offline Conversions API as FAIL (discontinued May 2025)
  • Flag missing CMP integration as Critical (Meta EU Consent Policy)
  • Weight ROAS / CPA above CTR / CVR when metrics disagree

Output

Write to ./reports/<client_id>/<YYYY-MM-DD>-meta-audit/META-ADS-REPORT.md.

First non-empty line:

SCORE: <0-100>/100 GRADE: <A|B|C|D|F> CLIENT: <client_id> PLATFORM: meta_ads PERIOD: <start>..<end>

Return: score + grade, category breakdown, full report path, anomaly alert list, EMQ improvement roadmap if any event < 8.0.

Changes

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.

  1. 11d ago First seen · 68 lines · 48 tokens per session scan A b158f0b21694

Subscribe to this mod's changes

audit-meta is an agent published in the GitHub repository Pauesome/Paid-Media-MCP (1 stars, last pushed 2mo ago), licensed MIT. It adds 48 tokens to every session and 586 once invoked, about $0.0002 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.