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 TrueClicks/claude-plugins --skill skill-139-ad-disapproval-monitoringgit clone --depth 1 https://github.com/TrueClicks/claude-pluginsWrote 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/trueclicks/claude-plugins/skill-139-ad-disapproval-monitoring)<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-139-ad-disapproval-monitoring"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-139-ad-disapproval-monitoring/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/trueclicks/claude-plugins/skill-139-ad-disapproval-monitoring"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-139-ad-disapproval-monitoring.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.00023 | $0.00700 |
| Opus 5.5 | $0.00009 | $0.00280 |
| Sonnet 5.5 | $0.00005 | $0.00140 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
skill-139-ad-disapproval-monitoring 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 21d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill 139: Ad Disapproval Monitoring
Purpose
Identify disapproved and limited ads that are not serving, prioritize by business impact, and provide resolution workflows. Prompt attention to disapprovals prevents revenue loss and ensures ad coverage across all ad groups.
Data Requirements
Data Source: Standard + Custom GAQL
Standard Data:
data/account/campaigns/*/*/ads.md- Ad approval status, policy issues
GAQL Query (for detailed policy info):
SELECT
campaign.name,
ad_group.name,
ad_group_ad.ad.id,
ad_group_ad.ad.type,
ad_group_ad.ad.final_urls,
ad_group_ad.policy_summary.approval_status,
ad_group_ad.policy_summary.review_status,
ad_group_ad.policy_summary.policy_topic_entries
FROM ad_group_ad
WHERE ad_group_ad.status != 'REMOVED'
AND ad_group_ad.policy_summary.approval_status IN ('DISAPPROVED', 'APPROVED_LIMITED', 'AREA_OF_INTEREST_ONLY')
Run via /google-ads:get-custom with query name ad_policy_issues.
Analysis Steps
- Read ad approval data: Extract status from ads.md files
- Identify disapprovals: List all ads with non-approved status
- Analyze policy topics: Categorize by violation type (editorial, trademark, destination, etc.)
- Assess impact: Flag ad groups with no remaining approved ads
- Prioritize resolution: Order by impact and fix complexity
Thresholds
| Condition | Severity |
|---|---|
| Ad group with 0 approved ads | Critical |
| High-spend campaign with disapproved ads | Critical |
| Multiple ads with same policy violation | Warning |
| Ads limited to specific regions | Warning |
| Ads under review > 3 days | Info |
Output
Short format (default):
## Ad Disapproval Audit
**Account:** [Name] | **Total Ads:** [X] | **Disapproved:** [Y]
### Ad Approval Summary
| Status | Count |
|--------|-------|
| Approved | [X] |
| Disapproved | [Y] |
| Limited | [Z] |
| Under Review | [W] |
### Critical - Ad Groups with No Active Ads
- **[Campaign/AdGroup]**: All [X] ads disapproved → Fix immediately
### Disapproved Ads
| Campaign | Ad Group | Policy Issue | Fix |
|----------|----------|--------------|-----|
| [Name] | [Name] | TRADEMARKS | Remove trademark |
| [Name] | [Name] | EDITORIAL | Fix capitalization |
### Resolution Priority
1. Fix [X] ad groups with no active ads
2. Address [Y] editorial issues (quick fixes)
3. Resolve [Z] policy violations
### Recommendations
1. Keep 2-3 approved ads per ad group as backup
2. Review landing pages for destination issues
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.
- 21d ago First seen · 94 lines · 23 tokens per session scan A 90c537b1e72e
skill-139-ad-disapproval-monitoring is a skill published in the GitHub repository TrueClicks/claude-plugins (2 stars, last pushed 22d ago), licensed MIT. It adds 23 tokens to every session and 700 once invoked, about $0.0001 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-10-08.
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…