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.
/plugin marketplace add chanktb/claude-google-ads/plugin install 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/skills/chanktb/claude-google-ads/google-ads)<a href="https://agentmods.dev/skills/chanktb/claude-google-ads/google-ads"><img src="https://agentmods.dev/badge/skills/chanktb/claude-google-ads/google-ads/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/chanktb/claude-google-ads/google-ads"><img src="https://agentmods.dev/badge/skills/chanktb/claude-google-ads/google-ads.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.00125 | $0.01600 |
| Opus 5 | $0.00063 | $0.00800 |
| Sonnet 5 | $0.00025 | $0.00320 |
| Haiku 4.5 | $0.00013 | $0.00160 |
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 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Ads — Router
The single entry point. Find out where the user is in the campaign lifecycle and hand off to the right sub-skill. Enforce the order so nothing runs on a broken foundation.
STEP 0 — Locate context
Look for account-context.yaml in the working directory (or a --context <path> the user gives).
- Missing → run
claude-google-ads:setupfirst. Nothing else runs without context. - Present → continue.
STEP 0b — Connection precheck (REQUIRED — don't run skills on a half-connected account)
Read the context connections block (or detect live). Before routing, confirm the prerequisites are set up;
the suite's value depends on real data, and it must never run on a gap silently (see the no-fabricate gate):
| Connection | Tier | If missing |
|---|---|---|
| Google Ads (read-only GAQL MCP) | MANDATORY | STOP. Nothing runs. Send the user to setup to connect a Google Ads MCP. |
| Store (Shopify/Woo/BigCommerce) | required for full value | Guide to connect (MCP or an Admin token in a .env). Without it: no real AOV / true-ROAS — those outputs render UNVERIFIED — connect store. |
| Merchant Center (ecom) | required for feed health | Guide to connect. Without it: product performance only, feed health (OOS/disapproval, D14-B) = UNVERIFIED. |
| GA4 | recommended | Guide to connect. Without it: no Ads-vs-GA4 value cross-check. |
| GSC | optional | Note only. |
If Google Ads is missing → stop and run setup. If a value-tier source (store/Merchant/GA4) is missing →
surface a one-line "connect these for full value" banner with the how-to, then proceed at reduced scope —
every output that needed the missing source is flagged UNVERIFIED, never fabricated. Don't quietly skip.
STEP 1 — Assess lifecycle stage
Run the context validator to read readiness, and scan the working dir for prior artifacts:
python ${CLAUDE_PLUGIN_ROOT}/skills/setup/scripts/validate_context.py ./account-context.yaml
Map state → the next sensible step:
| Readiness | Artifacts present | Likely next step |
|---|---|---|
| not setup-complete | — | setup (finish context) |
| setup-complete, no audit | — | audit and/or measurement |
| measurement = FAIL | measurement report | back to tracking fixes (block plan/build) |
| measurement OK, no plan | audit + measurement | plan |
| plan exists, no spec | GOOGLE-ADS-PLAN.md | builder-* for the chosen types |
| spec exists, not pushed | campaign-spec.json | pusher |
| campaign live | — | tracker (new) / optimizer (mature) |
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 · 100 lines · 125 tokens per session scan A e1bfe71093e0
google-ads is a skill published in the GitHub repository chanktb/claude-google-ads (11 stars, last pushed 2mo ago), licensed MIT. It adds 125 tokens to every session and 1,600 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.
Other skills, from other repositories
google-ads
A Google Ads guide for campaigns and advertising copy aimed at the Russian market in 2026. Google Ads is Google's paid advertising platform, and the guide covers formats such as search, video, app, shopping, and display ads.
markifact-overview
Reference — what Markifact is, what the MCP server exposes, and the discover→inspect→run pattern. Always loaded into the performance-marketer agent.
safe-write-operations
Reference — rules for safely executing write/destructive operations against ad accounts. Always loaded into the performance-marketer agent.
google-ads-ecommerce
Build and optimize Google Ads campaigns for ecommerce with Performance Max, Shopping feeds, conversion tracking, and Smart Bidding strategies for ROAS.
setup-conversion-tracking
Set up Converly conversion tracking end to end. Use when the user wants to track form submissions as conversions, send leads to an ad platform like Google Ads, Meta or Google Analytics, or set up Converly for the first time.
diagnose-missing-conversions
Find out why Converly conversions aren't showing up. Use when the user says tracking isn't working, conversions are missing, a form submission didn't appear, or an ad platform isn't receiving conversions.