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.
git clone --depth 1 https://github.com/Ad-Superpowers/ad-superpowers-pluginWrote 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/commands/ad-superpowers/ad-superpowers-plugin/audience-overlap-detector)<a href="https://agentmods.dev/commands/ad-superpowers/ad-superpowers-plugin/audience-overlap-detector"><img src="https://agentmods.dev/badge/commands/ad-superpowers/ad-superpowers-plugin/audience-overlap-detector.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.1 | $0.00023 | $0.01231 |
| Opus 5 | $0.00012 | $0.00616 |
| Sonnet 5 | $0.00005 | $0.00246 |
| Haiku 4.5 | $0.00002 | $0.00123 |
Grade A, and why
audience-overlap-detector 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 7d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Platforms: meta Tier: pro
This command requires the Ad Superpowers MCP connector to access your ad account data. Connect at https://app.adsuperpowers.ai if you haven't already.
Audience Overlap Detector
Detect and resolve audience overlap in Meta Ads campaigns
Conditional: if include_recommendations with detailed fix recommendations.
OUTPUT FORMAT (CRITICAL - follow this EXACT structure)
OVERLAP SUMMARY
| Metric | Value |
|---|---|
| Active Ad Sets Scanned | |
| High Overlap Pairs | |
| Medium Overlap Pairs | |
| Est. Monthly Budget Waste |
HIGH OVERLAP PAIRS (Action Required)
| Ad Set A | Ad Set B | Overlap Type | Severity | Combined Spend | Fix |
|---|---|---|---|---|---|
| (Sorted by combined spend descending) |
LOOKALIKE STACKING ISSUES
| Seed Audience | 1% LAL | 2% LAL | 3%+ LAL | Issue | Fix |
|---|---|---|---|---|---|
| Recommendation: Use non-overlapping bands (0-1%, 1-2%, 2-3%) or keep only the 1%. |
EXCLUSION GAPS
| Ad Set | Missing Exclusion | Impact | Priority |
|---|---|---|---|
| (Ad sets that should exclude certain audiences but don't) |
PROPER EXCLUSION HIERARCHY
Prospecting campaigns should exclude:
- All purchasers (180 days)
- All leads (90 days)
- Website visitors (if retargeting runs separately)
Retargeting campaigns should exclude:
- Recent purchasers (based on purchase cycle)
- Already converted leads (if lead gen)
ACTION PLAN
- [Highest impact fix - estimated savings]
- [Second fix]
- [Third fix]
EXECUTION STEPS
Step 1: Discover Account
meta_list_ad_accounts()
Step 2: Pull All Active Ad Sets with Targeting
meta_query(account_id="FROM_STEP_1", edge="adsets", params={"fields":"name,targeting,status,daily_budget,lifetime_budget,optimization_goal,campaign_id", "filtering":[{"field":"status","operator":"IN","value":["ACTIVE"]}], "limit":100})
Step 3: Pull Campaign Names for Context
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.
- 7d ago First seen · 123 lines · 23 tokens per session scan A b151a4a7a78d
audience-overlap-detector is a command published in the GitHub repository Ad-Superpowers/ad-superpowers-plugin (5 stars, last pushed 9d ago), licensed MIT. It adds 23 tokens to every session and 1,231 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-31.
Other commands, from other repositories
meta-audit
Full Meta Ads account audit, tailored to ecommerce or lead-gen automatically.
feed-audit
Audit Merchant Center feed quality — disapprovals, attributes, identifiers, custom labels.
setup
First-run setup for the ga-mcp-full MCP server — install the CLI if needed, then complete the browser login.
auth-logout
Clear cached Google Analytics OAuth credentials for the ga-mcp-full MCP server.
audit
Google Ads command — audit.
logout
Google Ads command — logout.