google-ads-plan

google-ads-plan is a skill for Claude Code from chanktb/claude-google-ads. It costs 116 tokens per session (1,522 once invoked), scanned A, original, MIT.

A Google Ads planning tool that turns a budget and business information into a campaign roadmap. It compares campaign types such as Search, branded Search, Performance Max, and Demand Gen, and estimates likely results when account data is available.

In plain words
What is it for?
Use it to plan a launch or expansion, choose campaign types and order, divide budgets, estimate conversions, cost per acquisition, or return on ad spend, and create a phased ramp-up plan.
Why use it?
It helps decide how to divide spending and what to launch first. It also flags broken conversion tracking before recommending new ad spend.

Skill for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: mentions subagents.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the claude-google-ads plugin — 15 skills, 15 commands shipped together

Good fit Use it to plan a launch or expansion, choose campaign types and order, divide budgets, estimate conversions, cost per acquisition, or return on ad spend, and create a phased ramp-up plan.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add chanktb/claude-google-ads
Claude Code
/plugin install claude-google-ads

Made for: Claude Code.

Or install claude-google-ads, the plugin that ships this one along with the rest of its 15 skills, 15 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 google-ads-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/chanktb/claude-google-ads/plan.svg)](https://agentmods.dev/skills/chanktb/claude-google-ads/plan)
Your own site
<a href="https://agentmods.dev/skills/chanktb/claude-google-ads/plan"><img src="https://agentmods.dev/badge/skills/chanktb/claude-google-ads/plan.svg" alt="Measured on agentmods" height="20"></a>
Per session 116 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,522 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.00116 $0.01522
Opus 5 $0.00058 $0.00761
Sonnet 5 $0.00023 $0.00304
Haiku 4.5 $0.00012 $0.00152

Measured 8d ago against content hash 0e65e33508de, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

google-ads-plan 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 8d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/forecaster.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/plan/SKILL.md · 90 lines

How it starts

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

Turn a budget + business context into a concrete plan and an honest forecast. Read everything from the context and the audit/measurement outputs — no hardcoding, no guessing where data exists.

STEP 0 — Load context + GATE

  1. Read account-context.yaml (budget, AOV, margin_tiers, brand_terms, vertical, guardrails) and the latest audit + measurement outputs from the working directory. If the context is missing, run setup first — never plan spend without it.
  2. Measurement gate: if measurement = FAIL, STOP — do not plan spend on broken tracking. Tell the user to fix tracking first. WARN is allowed but carried into the plan as a risk note.
  3. Confirm campaign_defaults.daily_budget (or ask). Output is written to the working directory.

Model dispatch (run cheap, decide expensive) — see ${CLAUDE_PLUGIN_ROOT}/references/model-tier-dispatch.md

  • Scout (haiku) — the forecaster.py run; reading existing campaign budgets.
  • Routine (sonnet) — STEP 1 mode-detection pull (existing campaigns + spend), STEP 4 deriving CPC/CVR from account data. Dispatch as general-purpose sub-agents; return raw, don't decide the mode.
  • Judge (main session) — STEP 0 measurement gate, the campaign mix + sequencing, budget split, forecast interpretation (band not promise), ramp roadmap, risks. The data is cheap; the plan is judgment.

STEP 1 — Detect mode: LAUNCH vs EXPANSION

Read existing ENABLED campaigns + their spend/performance. The plan differs sharply:

  • LAUNCH (no/low history) — start simple, lean on benchmarks, conservative ranges, one or two campaign types, no target ROAS during learning.
  • EXPANSION (established account) — read actual scale and find gaps. Read the real budget scale, don't assume small (e.g. a mature account may run $1k+/day across many campaigns). Recommend additions/reallocations against what already exists, not a from-scratch structure. State which mode you detected and why.

Read the full file on GitHub · 90 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 8d ago First seen · 90 lines · 116 tokens per session scan A 0e65e33508de

Subscribe to this mod's changes

google-ads-plan is a skill published in the GitHub repository chanktb/claude-google-ads (11 stars, last pushed 2mo ago), licensed MIT. It adds 116 tokens to every session and 1,522 once invoked, about $0.0006 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-30.

Related

Other skills, from other repositories