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-007-campaign-settings-hygienegit 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-007-campaign-settings-hygiene)<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-007-campaign-settings-hygiene"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-007-campaign-settings-hygiene/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-007-campaign-settings-hygiene"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-007-campaign-settings-hygiene.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.00028 | $0.00613 |
| Opus 5 | $0.00014 | $0.00307 |
| Sonnet 5 | $0.00006 | $0.00123 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
skill-007-campaign-settings-hygiene 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 10d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill 007: Campaign Settings Hygiene Check
Purpose
Audit all campaign-level settings including location targeting method, start/end dates, and network settings. A single misconfigured setting (e.g., targeting "interest in" rather than "presence in" a location) can waste significant budget.
Data Requirements
Data Source: Custom GAQL Required
Standard data includes basic campaign settings but may lack geo_target_type_setting. Custom GAQL provides complete settings.
GAQL Query:
SELECT
campaign.id,
campaign.name,
campaign.status,
campaign.start_date_time,
campaign.end_date_time,
campaign.geo_target_type_setting.positive_geo_target_type,
campaign.geo_target_type_setting.negative_geo_target_type,
campaign.network_settings.target_google_search,
campaign.network_settings.target_search_network,
campaign.network_settings.target_content_network
FROM campaign
WHERE campaign.status != 'REMOVED'
Run via /google-ads:get-custom with query name campaign_settings_audit.
Analysis Steps
- Check location targeting: Flag campaigns using
PRESENCE_OR_INTEREST(should bePRESENCEfor most businesses) - Check start/end dates: Flag enabled campaigns with past end dates or verify future start dates are intentional
- Check network settings: Verify Search campaigns don't have Display enabled; check Search Partners settings
- Review device targeting: Flag -100% device adjustments (fully excluded devices)
Thresholds
| Condition | Severity |
|---|---|
| Location method = PRESENCE_OR_INTEREST | Critical |
| Search campaign with Display enabled | Critical |
| End date in past, campaign still enabled | Warning |
| No language targeting set | Warning |
| Device 100% excluded | Info |
Output
Use Short format by default. Use Detailed if user requests comprehensive analysis.
Short:
## Campaign Settings Hygiene Audit
**Account:** [Name] | **Analyzed:** [X] campaigns | **Issues:** [Y]
### Critical ([Count])
- **[Campaign]**: Location targeting includes "interest in" → Change to PRESENCE only
- **[Campaign]**: Display Network enabled on Search → Disable
### Warnings ([Count])
- **[Campaign]**: End date [Date] has passed → Pause or remove end date
### Recommendations
1. Fix location targeting on [X] campaigns
2. Disable Display on Search campaigns
3. Review expired promotion campaigns
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.
- 10d ago First seen · 78 lines · 28 tokens per session scan A d3c532b10a03
skill-007-campaign-settings-hygiene is a skill published in the GitHub repository TrueClicks/claude-plugins (2 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 613 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…