Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/googleads/google-ads-api-developer-assistantnpx agentmods add commands/googleads/google-ads-api-developer-assistant/validate-gaqlWrote 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/commands/googleads/google-ads-api-developer-assistant/validate-gaql)<a href="https://agentmods.dev/commands/googleads/google-ads-api-developer-assistant/validate-gaql"><img src="https://agentmods.dev/badge/commands/googleads/google-ads-api-developer-assistant/validate-gaql/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/commands/googleads/google-ads-api-developer-assistant/validate-gaql"><img src="https://agentmods.dev/badge/commands/googleads/google-ads-api-developer-assistant/validate-gaql.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00025 | $0.00496 |
| Opus 5.5 | $0.00010 | $0.00198 |
| Sonnet 5.5 | $0.00005 | $0.00099 |
| Haiku 4.5 | $0.00003 | $0.00050 |
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 1mo 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
Validate GAQL (/validate-gaql)
Validates Google Ads Query Language (GAQL) queries against Google Ads API schemas using the 4-step validation protocol.
Instructions:
-
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.txtor the latest discovered version inclient_libs/. - Resolve the customer ID from
$ARGUMENTS,config/customer_id, or session context.
- Extract the query from
-
Execute Validation Protocol:
- Step 1: Schema Discovery - Verify that all selected and filtered fields exist in the resource schema using
client_libs/google-ads-pythonproto definitions orinspect_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
WHEREclause fields are inSELECT(unless date segments). - Ensure NO
ORoperator is used (GAQL only supportsAND; suggestINor separate queries). - Ensure NO
FROMclause is used forGoogleAdsFieldServicemetadata queries. - Ensure no SQL aggregation functions (
SUM(),COUNT()) are used. - Ensure segment renames are respected (in v23+,
segments.hourwas renamed tosegments.hour_of_day).
- Check that
- 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>"
- Step 1: Schema Discovery - Verify that all selected and filtered fields exist in the resource schema using
-
Output Format:
- Report Status:
PASSEDorFAILED. - List any syntax, schema, or structural errors with exact correction suggestions.
- Provide the corrected, copy-ready GAQL query in a code block.
- Report Status:
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.
- 1mo ago First seen · 35 lines · 25 tokens per session scan A b3c75a2aa506
validate-gaql is a command published in the GitHub repository googleads/google-ads-api-developer-assistant (102 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.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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
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.
specify
Create or update the feature specification from a natural language feature description.
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.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.
speckit.bug.test
Validate that a previously fixed bug is resolved and record the verification report.