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/assistant-tutorialnpx skills add googleads/google-ads-api-developer-assistant --skill assistant-tutorialgit 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.00018 | $0.00988 |
| Opus 5 | $0.00009 | $0.00494 |
| Sonnet 5 | $0.00004 | $0.00198 |
| Haiku 4.5 | $0.00002 | $0.00099 |
Grade A, and why
assistant-tutorial 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.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Ads API Developer Assistant Tutorial (Interactive Guide)
[!NOTE]
- If you want a real-world analogy and conceptual explanation for any Google Ads API concept, use the
/explain <concept>command.- If you want to walk through a process or workflow step-by-step, use the
/step-by-step <process>command.
Critical Directive for the Agent
When a user invokes /assistant-tutorial or requests this tutorial:
- NO MD SYNOPSIS FILES: You MUST NOT write any markdown files or artifacts summarizing the tutorial.
- ALWAYS INTERACTIVE: You MUST run this tutorial as an interactive, conversational experience.
- TOPIC SELECTION: Start by asking the user which specific topic they want to learn about first using an interactive question or message.
- PROGRESSIVE DISCLOSURE: Present information in small, manageable pieces. Ask checking questions or prompt the user to proceed before moving on to the next step.
- EXPLAIN ANSWER OPTION: Whenever you pose an interactive check question or quiz to the user, include a choice/option that allows them to ask the Assistant to answer and explain the answer.
Tutorial Content Reference
Topic 1: Core Principles & Constraints
- The "NO MUTATE" Read-Only Policy: The Assistant cannot execute mutate operations (such as create, update, or delete) directly. Instead, it provides the code for the mutate in the
~/saved/code/directory, which the user can run themselves or incorporate into their codebase. - API Versioning: All code and GAQL queries target the confirmed version in
config/api_version.txt.
Topic 2: Campaign Creation (Code Generation Workflow)
- Explain the generation & execution workflow.
- Show standard template structures.
- NO MUTATE Execution Warning: Remind the user that the Assistant is designed for read-only operations and cannot execute campaign creation mutate code directly.
Topic 3: Shared Sets (Exclusion Lists)
- Explain
SharedSet(reusable keyword/placement exclusion folders),SharedCriterion(items), andCampaignSharedSet(connector). - Describe relationships and benefits.
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 · 70 lines · 18 tokens per session scan A f6aecf885be1
assistant-tutorial 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 18 tokens to every session and 988 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
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
a-evolve
Apply A-Evolve's agentic evolution methodology to improve AI agent performance across runs. Use when the user wants to diagnose agent failures, generate targeted skills from error patterns, evolve system prompts, or accumulate episodic knowledge. Works standalone or inside AutoResearchClaw pipelines. Triggers on…
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…
📝 任务完成后归档
重要提醒: 每次完成复杂调试或开发任务后，主动执行此流程！ 将学到的经验归档为 skill，供以后参考。不要等用户提醒。.
deck-course-module
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
code-documenter
Use when adding docstrings, creating API documentation, or building documentation sites. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, tutorials, user guides.