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-030-ad-extension-coverage-auditgit 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-030-ad-extension-coverage-audit)<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-030-ad-extension-coverage-audit"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-030-ad-extension-coverage-audit/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-030-ad-extension-coverage-audit"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-030-ad-extension-coverage-audit.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.00022 | $0.00652 |
| Opus 5.5 | $0.00009 | $0.00261 |
| Sonnet 5.5 | $0.00004 | $0.00130 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
skill-030-ad-extension-coverage-audit 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill 030: Ad Extension Coverage Audit
Purpose
Ad extensions increase ad real estate and improve CTR by 10-15%. Missing extensions mean lost opportunities. This audit ensures comprehensive extension coverage at account, campaign, and ad group levels for all relevant extension types.
Data Requirements
Data Source: Standard
Standard Data:
data/account/ext_sitelinks.md- Sitelink extensionsdata/account/ext_callouts.md- Callout extensionsdata/account/ext_structured_snippets.md- Structured snippet extensionsdata/account/ext_call.md- Call extensionsdata/account/ext_price.md- Price extensionsdata/account/ext_promotion.md- Promotion extensionsdata/account/campaigns/*/campaign.md- Campaign settings
Reference GAQL:
SELECT
campaign.name,
campaign.status,
asset.type,
campaign_asset.status,
campaign_asset.field_type
FROM campaign_asset
WHERE campaign.status != 'REMOVED'
Use /google-ads:get-custom for account-level asset inventory or performance data.
Analysis Steps
- Inventory all extension types: Read ext_*.md files, categorize by type and linking level
- Check coverage requirements: Sitelinks (4+ recommended), Callouts (4+), Structured snippets (1+)
- Verify linking hierarchy: Account-level applies to all, campaign overrides account, ad group overrides campaign
- Assess extension status: Enabled vs Paused, Approved vs Disapproved
- Evaluate quality: Sitelinks with descriptions, unique callouts, relevant snippet headers
Thresholds
| Condition | Severity |
|---|---|
| No sitelinks at any level | Critical |
| No callouts at any level | Critical |
| Sitelinks < 4 | Warning |
| Callouts < 4 | Warning |
| No structured snippets | Warning |
| Disapproved extension | Critical |
Output
Short (default):
## Extension Coverage Audit
**Account:** [Name] | **Extension Types:** [X]/8 | **Issues:** [Y]
### Critical ([Count])
- **No [extension type]** at account level -> Add [X] [extension type]
### Warnings ([Count])
- **Sitelinks**: [X] (need [Y] more)
### Coverage Matrix
| Type | Account | Campaigns | Status |
|------|---------|-----------|--------|
| Sitelinks | X | X override | OK/Missing |
| Callouts | X | X | OK/Missing |
| Snippets | X | X | OK/Missing |
| Call | X | X | OK/Missing |
### Recommendations
1. [Priority action]
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 · 86 lines · 22 tokens per session scan A e9ce922f8eb3
skill-030-ad-extension-coverage-audit is a skill published in the GitHub repository TrueClicks/claude-plugins (2 stars, last pushed 22d ago), licensed MIT. It adds 22 tokens to every session and 652 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…