What is validate-gaql?

A validator for Google Ads Query Language, or GAQL, which is the query language used to request Google Ads data. It checks queries against the available fields and performs a live dry run without applying changes.

Use it to inspect field availability, check field compatibility, perform static checks, and test a query against a Google Ads customer account.

It catches invalid fields, incompatible selections, and unsupported query patterns before a query is presented or used.

validate-gaql — Skill by googleads

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/googleads/google-ads-api-developer-assistant/validate-gaql

Any agent

npx skills add googleads/google-ads-api-developer-assistant --skill validate-gaql

Clone the repo

git clone --depth 1 https://github.com/googleads/google-ads-api-developer-assistant

Made for: Claude Code, Codex.

Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 212 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.

Model	Per session	Once invoked
Fable 5	$0.00028	$0.00212
Opus 5	$0.00014	$0.00106
Sonnet 5	$0.00006	$0.00042
Haiku 4.5	$0.00003	$0.00021

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

Security

Grade A, and why

validate-gaql 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 3d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/validate_gaql.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

plugins/google-ads-api-developer-assistant/skills/validate-gaql/SKILL.md · 18 lines

What it actually says

Validate GAQL Skill

Before presenting or running any GAQL query, pass this 4-step sequence:

Schema Discovery: Verify field existence, selectability, and filterability using search_google_ads_fields.
Compatibility Check: Verify all selected fields are compatible with the primary resource.
Static Analysis:
- WHERE fields MUST be in SELECT (unless date segments).
- NO OR operator: Replace OR with IN or split into multiple queries.
- NO FROM in Metadata: Queries to GoogleAdsFieldService MUST NOT contain a FROM clause.
- Segment Renames: In v23+, segments.hour was renamed to segments.hour_of_day.
Runtime Dry Run: Execute API dry-run search request against target customer ID.

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

scripts/validate_gaql.py 9.6 KB runs code

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.

3d ago First seen · 18 lines · 28 tokens per session scan A 8e001bec8694

Subscribe to this mod's changes

validate-gaql is a skill published in the GitHub repository googleads/google-ads-api-developer-assistant (96 stars, last pushed 9d ago), licensed Apache-2.0. It adds 28 tokens to every session and 212 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.

Backend and APIs Testing

systematic-debugging

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

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens