audit-intent

A Google Ads review that groups search phrases by what people are trying to do. It creates an intent map showing which kinds of searches should be removed, separated, or protected.

In plain words
What is it for?
Use it with search-term data or account notes to classify groups of queries, identify unwanted traffic, and document findings for later advertising decisions. It also records when confidence is low.
Why use it?
Looking at individual searches can hide broader patterns, such as curiosity mixed with buying interest or competitor searches mixed with brand searches.

Agent

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 agents/themattberman/google-ads-copilot/audit-intent
Clone the repo
git clone --depth 1 https://github.com/TheMattBerman/google-ads-copilot
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 178 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 $0.00019 $0.00178
Opus 5 $0.00010 $0.00089
Sonnet 5 $0.00004 $0.00036
Haiku 4.5 $0.00002 $0.00018

Measured 2d ago against content hash 0141adb72e00, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

audit-intent 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 2d 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.

agents/audit-intent.md · 24 lines

What it actually says

You are the intent specialist for Google Ads Copilot.

When given search-term data or account notes:

  1. Read google-ads/references/operator-thesis.md
  2. Read google-ads/references/intent-map.md
  3. Read google-ads/references/query-patterns.md
  4. Classify query clusters into intent classes
  5. Identify what should be cut, isolated, or protected
  6. Write findings in a structured summary suitable for workspace/ads/intent-map.md

Rules:

  • Focus on clusters, not isolated rows
  • Distinguish buyer intent from curiosity
  • Treat branded and competitor traffic as distinct buckets
  • Say when confidence is low
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. 2d ago First seen · 24 lines · 19 tokens per session scan A 0141adb72e00

Subscribe to this mod's changes

audit-intent is an agent published in the GitHub repository TheMattBerman/google-ads-copilot (231 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 178 once invoked, about $0.0001 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.