skill-102-frequency-capping-management

skill-102-frequency-capping-management is a skill for Claude Code from TrueClicks/claude-plugins. It costs 32 tokens per session (549 once invoked), scanned A, original, MIT.

A review of frequency caps, which limit how many times one person can see an ad during a set period. It focuses on active Display and Video campaigns.

In plain words
What is it for?
Use it to inspect cap settings and compare impressions, clicks, conversions, cost, and estimated unique reach for recent campaigns.
Why use it?
It helps prevent repeated ads from wasting impressions and annoying people who are unlikely to respond.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the google-ads plugin — 145 skills, 4 commands shipped together

Good fit Use it to inspect cap settings and compare impressions, clicks, conversions, cost, and estimated unique reach for recent campaigns.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/trueclicks/claude-plugins/skill-102-frequency-capping-management
Install

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.

Any agent
npx skills add TrueClicks/claude-plugins --skill skill-102-frequency-capping-management
Clone the repo
git clone --depth 1 https://github.com/TrueClicks/claude-plugins

Made for: Claude Code.

Or install google-ads, the plugin that ships this one along with the rest of its 145 skills, 4 commands.

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 skill-102-frequency-capping-management

README.md
[![agentmods](https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-102-frequency-capping-management/github.svg)](https://agentmods.dev/skills/trueclicks/claude-plugins/skill-102-frequency-capping-management)
Your own site
<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-102-frequency-capping-management"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-102-frequency-capping-management/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 skill-102-frequency-capping-management

Your own site · 80×15
<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-102-frequency-capping-management"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-102-frequency-capping-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 549 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.00032 $0.00549
Opus 5.5 $0.00013 $0.00220
Sonnet 5.5 $0.00006 $0.00110
Haiku 4.5 $0.00003 $0.00055

Measured 21d ago against content hash fe63e9b1ad4e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

skill-102-frequency-capping-management 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.

plugins/google-ads/skills/skill-102-frequency-capping-management/SKILL.md · 75 lines

How it starts

The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skill 102: Frequency Capping Management

Purpose

Set appropriate frequency caps to prevent ad fatigue and wasted impressions. Uncapped remarketing wastes spend on users who have decided not to convert and damages brand perception.

Data Requirements

Data Source: Custom GAQL Required

GAQL Query:

SELECT
  campaign.name,
  campaign.frequency_caps,
  metrics.impressions,
  metrics.clicks,
  metrics.conversions,
  metrics.cost_micros
FROM campaign
WHERE campaign.advertising_channel_type IN ('DISPLAY', 'VIDEO')
  AND campaign.status = 'ENABLED'
  AND segments.date DURING LAST_30_DAYS

Run via /google-ads:get-custom with query name frequency_analysis.

Standard Data:

  • data/account/campaigns/*/campaign.md - Campaign settings

Analysis Steps

  1. Identify Display/Video Campaigns: Filter for campaigns where frequency capping applies
  2. Check Current Cap Settings: Review frequency cap configurations
  3. Analyze Reach vs. Frequency: Compare impressions to estimated unique reach
  4. Benchmark Against Best Practices: 3-5/week for remarketing, 2-3/week for prospecting

Thresholds

Condition Severity
No frequency cap on remarketing campaign Critical
Caps above 10 impressions/week Warning
No frequency cap on any Display campaign Warning
Caps below 2/week (under-exposure) Info

Output

Short (default):

## Frequency Capping Audit
**Account:** [name] | **Display/Video Campaigns:** [count] | **Without Caps:** [count]

### Critical
- **[campaign]**: No frequency cap - Unlimited impressions per user

### Warnings
- **[campaign]**: Cap at 15/week - Reduce to 5/week
- **[count] campaigns without caps** - Add 3-5 impressions/week

### Recommendations
1. Set 5 impressions/week cap on all remarketing campaigns
2. Set 3 impressions/week cap on prospecting Display
3. Consider 3/week cap for YouTube TrueView

Detailed adds:

  • Campaign frequency cap inventory
  • Recommended caps by campaign type table
  • Estimated wasted impressions from over-exposure
  • Layered approach recommendation (weekly + daily)

Read the full file on GitHub · 75 lines

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. 21d ago First seen · 75 lines · 32 tokens per session scan A fe63e9b1ad4e

Subscribe to this mod's changes

skill-102-frequency-capping-management is a skill published in the GitHub repository TrueClicks/claude-plugins (2 stars, last pushed 22d ago), licensed MIT. It adds 32 tokens to every session and 549 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.

Related

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens