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 commands/googleads/google-ads-api-developer-assistant/inspect-objectgit 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.00017 | $0.00347 |
| Opus 5 | $0.00009 | $0.00173 |
| Sonnet 5 | $0.00003 | $0.00069 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
inspect-object 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
Inspect Object (/inspect-object)
Dynamically inspects the fields, data types, nested messages, and Enum values of any Google Ads API object using client_libs/google-ads-python proto definitions.
Instructions:
-
Extract Parameters:
- Extract the object name from
$ARGUMENTS(e.g.Campaign,AdGroupCriterion,CampaignStatusEnum,AdGroupAd,BiddingStrategy). - If not provided, prompt the user for the object, message, or Enum name to inspect.
- Resolve API version from
config/api_version.txtor default to the latest discovered version.
- Extract the object name from
-
Execute Inspection:
- Run the inspection script:
python3 skills/inspect-object/scripts/inspect_object.py --name "$ARGUMENTS" --api_version "<api_version>" - If the script is unavailable in the environment, inspect the proto files directly in
client_libs/google-ads-python/google/ads/googleads/<api_version>/.
- Run the inspection script:
-
Output Format:
- Object Type: Identify whether the symbol is a Resource, Message, or Enum.
- Selectable / Filterable Fields: List core fields with data types and descriptions.
- Enum Values: For Enum types, list all possible values and their meanings.
- Nested Protobuf Messages: Show the structure of sub-messages.
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 · 28 lines · 17 tokens per session scan A 392e8d1a1205
inspect-object 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 17 tokens to every session and 347 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.