What is google-ads-setup?

A setup command for configuring credentials used by the Google Ads API, the interface for managing Google advertising accounts. It covers developer, service-account, customer, and manager-account details.

Use it to enter and store Google Ads credentials locally, configure an account or manager account, and test the API connection.

It guides the initial connection and helps verify access before campaign-management work begins.

google-ads-setup — Command for Claude Code by eneelkant

Install

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.

Clone the repo

git clone --depth 1 https://github.com/eneelkant/google-ads-claude-plugin

Made for: Claude Code.

Or install google-ads-manager, the plugin that ships this one along with the rest of its 1 skill, 1 command.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/eneelkant/google-ads-claude-plugin/google-ads-setup/github.svg)](https://agentmods.dev/commands/eneelkant/google-ads-claude-plugin/google-ads-setup)

Your own site

<a href="https://agentmods.dev/commands/eneelkant/google-ads-claude-plugin/google-ads-setup"><img src="https://agentmods.dev/badge/commands/eneelkant/google-ads-claude-plugin/google-ads-setup/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/eneelkant/google-ads-claude-plugin/google-ads-setup"><img src="https://agentmods.dev/badge/commands/eneelkant/google-ads-claude-plugin/google-ads-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 154 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00000	$0.00154
Opus 5.5	$0.00000	$0.00062
Sonnet 5.5	$0.00000	$0.00031
Haiku 4.5	$0.00000	$0.00015

Measured 29d ago against content hash 0d187a62b217, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

google-ads-setup 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 29d 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.

google-ads-manager/commands/google-ads-setup.md · 18 lines

What it actually says

Google Ads Setup

Use this command to configure Google Ads API credentials for the universal Google Ads MCP server.

The setup should guide the user through:

Cloning the public repository and running uv sync at the repo root
Google Ads Developer Token
Google Cloud service account credentials
Google Ads Customer ID
Login Customer ID, if using an MCC account
Securely storing credentials in a local .env (never commit it)
Connecting Claude (or another MCP client) via the examples in clients/ and docs/clients/

Never request users to paste credentials into a public GitHub repository.

After configuration, verify that the Google Ads API connection works before attempting campaign management operations.

Changes

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.

29d ago Changed · +2 lines 0d187a62b217
2mo ago First seen · 16 lines · 0 tokens per session scan A 61fe98e20556

Subscribe to this mod's changes

google-ads-setup is a command published in the GitHub repository eneelkant/google-ads-claude-plugin (1 stars, last pushed 29d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 154 tokens. 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-31.

Marketing and SEO

google-ads-setup next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
google-ads-setupeneelkant/google-ads-claude-plugin	Command	1	29d ago	Apache-2.0	A	0	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code