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 agentmods add skills/googleads/google-ads-api-developer-assistant/explainnpx skills add googleads/google-ads-api-developer-assistant --skill explaingit clone --depth 1 https://github.com/googleads/google-ads-api-developer-assistantWhat 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 | $0.00022 | $0.00402 |
| Opus 5 | $0.00011 | $0.00201 |
| Sonnet 5 | $0.00004 | $0.00080 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
explain 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.
What it actually says
Explain
Use this skill to explain Google Ads API concepts, code snippets, or queries. This ensures explanations are accessible to both technical and non-technical stakeholders while maintaining technical accuracy.
Protocol
When asked to explain a concept, you MUST structure your response with the following four sections:
1. The Big Picture
Provide a high-level summary of the fundamental problem this concept solves for the entire system. Limit this to 1-2 direct sentences.
2. Analogy [MANDATORY]
You MUST use a real-world, non-technical analogy to explain the concept. Map the technical components to everyday objects or processes.
- Constraint: Do not use technical jargon in the analogy itself.
3. Interconnectedness
Describe how this concept interacts with other core components of the Google Ads API. Mention specific resources or services it links to.
4. Simple Language
Create a distinct section titled "Simple Language" to summarize the concept in a way that is accessible to non-technical users, without losing technical correctness.
Example Explanation
Concept: click_view
The Big Picture
click_view retrieves performance metrics at the individual click level, allowing advertisers to trace conversions back to the specific click event.
Analogy
Think of a standard report as your monthly credit card statement summary (which only shows the total spent). click_view is the itemized receipt from a specific store visit, showing exactly what was bought, when, and the exact price for that single transaction.
Interconnectedness
It links directly to campaign and ad_group via their resource names, allowing you to associate individual click data with the hierarchy of your ad account.
Simple Language
It lets you see details for every single click on your ad, rather than just summaries of clicks over time.
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.
- 2d ago First seen · 44 lines · 22 tokens per session scan A db0ad06c20ab
explain is a skill published in the GitHub repository googleads/google-ads-api-developer-assistant (96 stars, last pushed 8d ago), licensed Apache-2.0. It adds 22 tokens to every session and 402 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…