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.
git clone --depth 1 https://github.com/chanktb/claude-google-adsWrote 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/commands/chanktb/claude-google-ads/google-ads)<a href="https://agentmods.dev/commands/chanktb/claude-google-ads/google-ads"><img src="https://agentmods.dev/badge/commands/chanktb/claude-google-ads/google-ads.svg" alt="Measured on agentmods" 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.00034 | $0.00584 |
| Opus 5 | $0.00017 | $0.00292 |
| Sonnet 5 | $0.00007 | $0.00117 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
google-ads 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 7d 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.
What it actually says
/google-ads
Router / "where am I" entry point. For a specific step, prefer the dedicated command:
/claude-google-ads:setup, :audit, :measurement, :plan, :pmax, :search, :branded, :demandgen,
:push, :track, :optimize, :routine, :experiment, :assets. (Type /claude-google-ads to see them
all in the menu — you don't memorize the names.)
Use this /google-ads command when the user is unsure where they are: read the context, report the stage,
and tell them the single dedicated command to run next.
Route the user's request to the correct sub-skill of the claude-google-ads plugin.
Routing logic
- Check for
account-context.yamlin the working directory (or the path the user gives).- If missing -> invoke
claude-google-ads:setupfirst. Nothing else runs without context.
- If missing -> invoke
- Match intent -> skill:
- "audit", "score my account", "what's wrong" ->
claude-google-ads:audit - "is my tracking right", "conversions", "GA4 import" ->
claude-google-ads:measurement - "plan", "budget", "what campaigns should I run", "launch" ->
claude-google-ads:plan - "build pmax", "performance max" ->
claude-google-ads:builder-pmax - "build search" ->
claude-google-ads:builder-search - "branded search", "brand campaign" ->
claude-google-ads:builder-branded-search - "demand gen" ->
claude-google-ads:builder-demand-gen - "push", "export", "upload to google ads" ->
claude-google-ads:pusher - "how's it doing", "pacing", "learning phase" ->
claude-google-ads:tracker - "optimize", "improve roas", "negatives", "raise tROAS" ->
claude-google-ads:optimizer - "experiment", "A/B test", "split test" ->
claude-google-ads:experiments - "ad copy", "assets", "headlines", "creative" ->
claude-google-ads:assets
- "audit", "score my account", "what's wrong" ->
- If ambiguous, ask one clarifying question, then route.
$ARGUMENTS
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.
- 7d ago First seen · 37 lines · 34 tokens per session scan A f6bccbee22e3
google-ads is a command published in the GitHub repository chanktb/claude-google-ads (11 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 584 once invoked, about $0.0002 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.
Other commands, from other repositories
diagnose-underperformer
Diagnose why a specific Google Ads or Meta Ads campaign / ad set / ad is underperforming and prescribe the next concrete action. Use when the user says something like "why is X not converting?", "this campaign is wasting money", or "why are impressions so low?". Read-only — no changes are made.
edit-meta-creative
Edit a Meta ad's creative content — landing page URL, primary text, headline, description, CTA, link description — across one ad or many. Use when the user says "change the URL on my ads", "update the copy", "swap the CTA", or anything that changes what an existing Meta ad shows. Meta does not allow in-place creative…
launch-google-search
Launch a complete Google Ads Search campaign — campaign, ad group, responsive search ads, keywords, sitelinks, callouts, and negatives — built paused and ready to review. Use when the user wants to spin up a new Search campaign on Google Ads.
launch-meta-campaign
Launch a complete Meta Ads campaign — campaign, ad set, and ad(s) — built paused and ready to review. Use when the user wants a new Facebook/Instagram campaign.
launch-pmax
Launch a Google Ads Performance Max campaign with a complete asset group, audience signals, and (for ecom) listing groups. Built paused for review. Use when the user wants a new PMax campaign.
negative-keyword-sweep
Find wasted spend in Google Ads search terms and add negatives at the right scope (account list, campaign, or ad group). Use when the user says "find junk keywords", "stop wasting on bad searches", or wants a search-terms cleanup.