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/fmind/dot/google-adsnpx skills add fmind/dot --skill google-adsgit clone --depth 1 https://github.com/fmind/dotWrote 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/skills/fmind/dot/google-ads)<a href="https://agentmods.dev/skills/fmind/dot/google-ads"><img src="https://agentmods.dev/badge/skills/fmind/dot/google-ads.svg" alt="Measured on agentmods" 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 | $0.00046 | $0.00522 |
| Opus 5 | $0.00023 | $0.00261 |
| Sonnet 5 | $0.00009 | $0.00104 |
| Haiku 4.5 | $0.00005 | $0.00052 |
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.
What it actually says
Google Ads
Google's advertising developer surface has four families: the Google Ads API (campaigns, reporting, an official MCP server), the Data Manager API (audiences and conversions), the Google Mobile Ads SDK (AdMob and Ad Manager in apps), and the IMA SDK (video ads). Marketing strategy is out of scope; this skill routes the engineering task to the ads group of the official catalog.
Gotchas
- Credentials: the Ads API needs a developer token plus an OAuth client; keep both in environment variables or Secret Manager.
- Money moves: use a test account and
validate_onlyrequests before touching a live account; every mutation can spend budget. - MCP: the Ads MCP server runs locally with the same credentials; configure it per agent-mcp.
Official Skills
Upstream: google/skills (skills/ads group; pick by family: API quickstart or diagnostics, Data Manager ingestion, mobile SDK formats and migration, IMA client-side or DAI). List the current release, then install what the task needs at project scope after reviewing the snapshot (see agent-skills):
skills add https://github.com/google/skills/tree/main/skills/ads --list
skills add https://github.com/google/skills/tree/main/skills/ads --skill <name> -y
Documentation
- Google Ads API · AdMob · IMA SDK
- Companion skills: google-analytics, google-developer, gcloud, agent-mcp.
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 · 35 lines · 46 tokens per session scan A 4407c5b0b9ef
google-ads is a skill published in the GitHub repository fmind/dot (4 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 522 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
go-stack
Build Go projects, libraries, CLIs, TUIs, web apps, or ADK agents with the standard package layout and pinned tooling.
python-stack
Build typed Python projects with uv, Ruff, ty, pytest, Litestar, and Typer. Use for packages, CLIs, web apps, tests, typing, or API verification.
k8s-local
Create and manage local Kubernetes clusters (k3d or kind) and deploy to them with kubectl, helm, helmfile, and skaffold. Use for local k8s cluster setup, dev loops, and debugging.
chezmoi
Manage chezmoi dotfiles: source naming, Go templates, age-encrypted secrets, and the edit-source then apply/diff workflow.
hugo
Canonical Hugo static-site stack with the Hextra docs theme — Hugo Modules, mise tasks, dprint, lefthook, and GitHub Pages deploy. Use for documentation sites, project docs, and static websites.
mise
Configure pinned mise tools and canonical install, format, check, test, build, and watch tasks shared by hooks and CI.