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.
npx skills add TheMattBerman/google-ads-copilot --skill google-ads-landing-reviewgit clone --depth 1 https://github.com/TheMattBerman/google-ads-copilotWrote 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/themattberman/google-ads-copilot/google-ads-landing-review)<a href="https://agentmods.dev/skills/themattberman/google-ads-copilot/google-ads-landing-review"><img src="https://agentmods.dev/badge/skills/themattberman/google-ads-copilot/google-ads-landing-review/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/themattberman/google-ads-copilot/google-ads-landing-review"><img src="https://agentmods.dev/badge/skills/themattberman/google-ads-copilot/google-ads-landing-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00086 | $0.03808 |
| Opus 5 | $0.00043 | $0.01904 |
| Sonnet 5 | $0.00017 | $0.00762 |
| Haiku 4.5 | $0.00009 | $0.00381 |
Grade A, and why
google-ads-landing-review 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 11d 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 — 423 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Ads Landing Review
Why this skill exists
"The landing page isn't converting" is the most common complaint in Google Ads. But it hides two completely different root causes:
- Tracking problem — conversions ARE happening but aren't being counted.
- Path problem — the visitor arrives but the page fails them.
Most operators (and most clients) assume path failure when the numbers look bad. Half the time, it's a tracking failure. Conflating the two wastes months.
This skill separates them.
Read first:
google-ads/references/operator-thesis.mdgoogle-ads/references/tracking-playbook.mdgoogle-ads/references/structure-playbook.md
Read workspace if available:
workspace/ads/account.mdworkspace/ads/goals.mdworkspace/ads/findings.mdworkspace/ads/drafts/_index.md— check for existing tracking drafts
Diagnostic Model: Two Forks
"Landing page isn't converting"
│
┌────┴────┐
│ │
FORK A FORK B
Tracking Path/UX
│ │
Is the Is the page
signal actually
correct? failing?
Always run Fork A first. If tracking is broken, Fork B conclusions are unreliable.
Fork A: Tracking Diagnosis (Is the signal trustworthy?)
What to check
1. Does a conversion action exist for the goal on this page?
- Is there a conversion action configured for the form/call/purchase that this landing page is supposed to produce?
- Is it set as primary (
include_in_conversions_metric = TRUE)? - Is the counting type correct?
2. Does the tag actually fire?
- Is the Google Ads conversion tag (or GA4 event imported to Google Ads) present on the confirmation/thank-you page?
- Does the tag fire when the user completes the action? (Google Tag Assistant, network tab, or manual test)
- Is the tag firing on the WRONG page? (e.g., firing on page load of the form page instead of the thank-you page)
3. Is the conversion path end-to-end intact?
- Click on ad → landing page → form/CTA → thank-you page → tag fires → conversion recorded
- Where does the chain break?
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.
- 11d ago First seen · 423 lines · 86 tokens per session scan A 6e4b8866f6d2
google-ads-landing-review is a skill published in the GitHub repository TheMattBerman/google-ads-copilot (233 stars, last pushed 3mo ago), licensed MIT. It adds 86 tokens to every session and 3,808 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…
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…