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/squadcodercom/squadcoder/google-adsnpx skills add squadcodercom/squadcoder --skill google-adsgit clone --depth 1 https://github.com/squadcodercom/squadcoderWhat 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.00262 | $0.03700 |
| Opus 5 | $0.00131 | $0.01850 |
| Sonnet 5 | $0.00052 | $0.00740 |
| Haiku 4.5 | $0.00026 | $0.00370 |
Grade A, and why
google-ads 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 yesterday.
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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Ads — Pro Playbook
A practitioner's guide to architecting, launching, and scaling Google Ads accounts. Use real
platform terminology and current features. When the user has connected the bundled google-ads MCP
(uvx googleads/google-ads-mcp), drive it for live account operations: read with gads_google_ads_search_google_ads
(GAQL), build with the gads_campaign_*, gads_ad_group_*, gads_asset_group_*, gads_bidding_strategy_*
and gads_keyword_* tools, and pull keyword ideas with gads_keyword_plan_idea_*. Always read before you
write, and stage large changes through gads_batch_job_*.
Reuse note: this skill is authored fresh for SquadCoder; structure informed by public MIT Google Ads skill packs (e.g. TheMattBerman/google-ads-copilot, nowork-studio/NotFair).
1. Account & campaign structure
Hierarchy: MCC (manager) → Account → Campaign → Ad group / Asset group → Ads / Assets → Keywords / Audiences.
Pick the campaign type by intent and inventory:
- Search — high-intent text ads on the SERP. The backbone of most accounts. Use intent-tight ad groups.
- Performance Max (PMax) — one campaign serving all Google inventory (Search, Shopping, Display, YouTube, Discover, Gmail, Maps) via asset groups + audience signals. Goal-based; great for ecommerce + lead-gen once you have conversion data. It cannibalizes Shopping/brand Search, so guard brand terms.
- Shopping — product ads from a Merchant Center feed. Standard Shopping gives priority/placement control; PMax replaces "Smart Shopping". Use feed quality (titles, GTINs, product types) as your lever.
- Demand Gen — visually rich social-style ads on YouTube (in-feed, Shorts), Discover, and Gmail. Use for mid-funnel demand creation with lookalike ("similar") segments and your 1st-party lists.
- Display — GDN banners/responsive display. Cheap reach + remarketing; weak for cold prospecting alone.
- YouTube / Video — objectives: brand awareness/reach, consideration (in-stream skippable, in-feed), action (Video action campaigns / VAC). Use bumpers (6s) for frequency, skippable in-stream for storytelling.
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.
- yesterday First seen · 218 lines · 262 tokens per session scan A 34a42c2659b9
google-ads is a skill published in the GitHub repository squadcodercom/squadcoder (11 stars, last pushed 2mo ago), licensed MIT. It adds 262 tokens to every session and 3,700 once invoked, about $0.0013 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
write-zot-themes
Help the user create, install, or package zot themes, including theme-only extensions.
python-testing
Python testing best practices using pytest including fixtures, parametrization, mocking, coverage analysis, async testing, and test organization. Use when writing or improving Python tests.
database-migrations
Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Django, TypeORM, golang-migrate). Use when planning or implementing database schema changes.
docker-patterns
Docker and Docker Compose patterns for local development, container security, networking, volume strategies, and multi-service orchestration. Use when setting up containerized development environments or reviewing Docker configurations.
python-patterns
Python-specific design patterns and best practices including protocols, dataclasses, context managers, decorators, async/await, type hints, and package organization. Use when working with Python code to apply Pythonic patterns.
st-full-workflow
Use when the user asks to run the complete end-to-end Strikethroo workflow for a work order in one shot in this repository — triggers include full workflow, end-to-end, plan and execute, do everything, run the whole strikethroo workflow. Do not use when the user wants only one stage (create a plan, generate tasks, or…