google-ads-draft-summary

google-ads-draft-summary is a skill for Claude Code, Codex from TheMattBerman/google-ads-copilot. It costs 65 tokens per session (1,968 once invoked), scanned A, original, MIT.

A single prioritised list of pending Google Ads changes. It ranks drafts by likely impact, risk, and order of application, and shows dependencies and blocked actions.

In plain words
What is it for?
Use it before a review session or when returning to an account. It summarises proposed and approved drafts, recommends an apply order, and gives the current backlog view.
Why use it?
Separate draft files do not show what should be reviewed or applied first, especially when one change depends on another.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/themattberman/google-ads-copilot/google-ads-draft-summary
Any agent
npx skills add TheMattBerman/google-ads-copilot --skill google-ads-draft-summary
Clone the repo
git clone --depth 1 https://github.com/TheMattBerman/google-ads-copilot

Made for: Claude Code, Codex.

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-draft-summary

README.md
[![agentmods](https://agentmods.dev/badge/skills/themattberman/google-ads-copilot/google-ads-draft-summary.svg)](https://agentmods.dev/skills/themattberman/google-ads-copilot/google-ads-draft-summary)
Your own site
<a href="https://agentmods.dev/skills/themattberman/google-ads-copilot/google-ads-draft-summary"><img src="https://agentmods.dev/badge/skills/themattberman/google-ads-copilot/google-ads-draft-summary.svg" alt="Measured on agentmods" height="20"></a>
Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,968 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00065 $0.01968
Opus 5 $0.00032 $0.00984
Sonnet 5 $0.00013 $0.00394
Haiku 4.5 $0.00006 $0.00197

Measured 6d ago against content hash 2aa4a62c77d3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

google-ads-draft-summary 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 6d 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.

skills/google-ads-draft-summary/SKILL.md · 246 lines

How it starts

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

Why this skill exists

After an audit, search-term review, or tracking diagnosis, the copilot produces individual draft files. But individual files don't answer the operator's real question:

"I have 20 minutes. What should I review and apply first?"

This skill answers that.

Read first:

  • drafts/DRAFTS.md — draft system documentation

Read workspace:

  • workspace/ads/drafts/_index.md — current queue
  • All workspace/ads/drafts/*.md — individual draft files
  • workspace/ads/account.md — account context
  • workspace/ads/findings.md — for tracking confidence context

What This Produces

A Draft Summary — a single document that:

  1. Lists every pending draft (status: proposed or approved)
  2. Classifies each by priority, impact, risk, and reversibility
  3. Shows dependency chains (what must be applied before what)
  4. Produces a recommended apply order (the sequence an operator should follow)
  5. Flags blocked actions (e.g., budget scaling blocked by tracking problems)
  6. Estimates total impact of applying all pending changes

This is the current backlog snapshot, not the audit-run packet. _summary.md should always reflect the latest pending queue. Durable audit packets belong in _batch-*.md.


Priority Classification

Each draft gets a priority level based on these criteria:

P0 — Fix First (Blocking)

  • Tracking problems that gate all other decisions
  • Actively harmful configurations (e.g., paying for store visits as conversions)
  • Budget bleeding on clearly wrong traffic
  • Apply these before anything else

P1 — Quick Wins (High Confidence, Easy, High Impact)

  • Clear negative keyword additions with significant waste (>$100/month)
  • Keyword pauses with obvious waste
  • Simple tracking cleanup (remove micro-conversion from primary)
  • Apply these in the same session as P0

P2 — Strategic Moves (Requires Thought)

  • Structure changes (campaign splits, ad group reorganization)
  • Budget reallocation between campaigns
  • Landing page changes
  • Schedule a focused review session for these

Read the full file on GitHub · 246 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. 6d ago First seen · 246 lines · 65 tokens per session scan A 2aa4a62c77d3

Subscribe to this mod's changes

google-ads-draft-summary is a skill published in the GitHub repository TheMattBerman/google-ads-copilot (231 stars, last pushed 2mo ago), licensed MIT. It adds 65 tokens to every session and 1,968 once invoked, about $0.0003 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

systematic-debugging

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

obra/superpowers · 21 tokens

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

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

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens