agentmods.dev

validate-gaql

A command that checks Google Ads Query Language queries against Google Ads API rules. GAQL is the query language used to request Google Ads data.

In plain words
What is it for?
Use it to perform schema checks, compatibility checks, static analysis, and live API dry-runs on GAQL queries.
Why use it?
It catches invalid fields, incompatible data selections, and query-structure problems before a query is used.

Command

96 8d ago A scan 25 tokens original Apache-2.0
View the source file googleads/google-ads-api-developer-assistant
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 commands/googleads/google-ads-api-developer-assistant/validate-gaql
Clone the repo
git clone --depth 1 https://github.com/googleads/google-ads-api-developer-assistant
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 496 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.00025 $0.00496
Opus 5 $0.00013 $0.00248
Sonnet 5 $0.00005 $0.00099
Haiku 4.5 $0.00003 $0.00050

Measured 2d ago against content hash b3c75a2aa506, 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 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.

plugins/google-ads-api-developer-assistant/commands/validate-gaql.md · 35 lines

What it actually says

Validate GAQL (/validate-gaql)

Validates Google Ads Query Language (GAQL) queries against Google Ads API schemas using the 4-step validation protocol.

Instructions:

  1. Extract Parameters:

    • Extract the query from $ARGUMENTS. If not provided, prompt the user for the GAQL query to validate.
    • Resolve the target API version from config/api_version.txt or the latest discovered version in client_libs/.
    • Resolve the customer ID from $ARGUMENTS, config/customer_id, or session context.

  2. Execute Validation Protocol:

    • Step 1: Schema Discovery - Verify that all selected and filtered fields exist in the resource schema using client_libs/google-ads-python proto definitions or inspect_object.py.
    • Step 2: Compatibility Check - Verify that all metrics, segments, and attributed resources are selectable together with the primary resource.
    • Step 3: Static Analysis:
      • Check that WHERE clause fields are in SELECT (unless date segments).
      • Ensure NO OR operator is used (GAQL only supports AND; suggest IN or separate queries).
      • Ensure NO FROM clause is used for GoogleAdsFieldService metadata queries.
      • Ensure no SQL aggregation functions (SUM(), COUNT()) are used.
      • Ensure segment renames are respected (in v23+, segments.hour was renamed to segments.hour_of_day).
    • Step 4: Dry-Run Execution (if credentials and customer ID are available): Run skills/validate-gaql/scripts/validate_gaql.py: 
      python3 skills/validate-gaql/scripts/validate_gaql.py --query "<query>" --customer_id "<customer_id>" --api_version "<api_version>"

  3. Output Format:

    • Report Status: PASSED or FAILED.
    • List any syntax, schema, or structural errors with exact correction suggestions.
    • Provide the corrected, copy-ready GAQL query in a code block.
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 · 35 lines · 25 tokens per session scan A b3c75a2aa506

Subscribe to this mod's changes

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

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

constitution

Create or update the project constitution from interactive or provided principle inputs.

github/spec-kit · 13 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens