get-cids

A command that lists the customer account IDs beneath a Google Ads manager account, also called an MCC. It shows the account hierarchy, including client accounts and sub-manager accounts.

In plain words
What is it for?
Use it to discover all child accounts, understand their nesting and names, and export the hierarchy to CSV.
Why use it?
It removes the need to inspect accounts one by one when a manager account controls many others. The result can also be saved as a CSV file for later use.

Command

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.

agentmods
npx agentmods add commands/googleads/google-ads-api-developer-assistant/get-cids
Clone the repo
git clone --depth 1 https://github.com/googleads/google-ads-api-developer-assistant
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 304 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00019 $0.00304
Opus 5 $0.00010 $0.00152
Sonnet 5 $0.00004 $0.00061
Haiku 4.5 $0.00002 $0.00030

Measured 2d ago against content hash 86e24e7fc003, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

get-cids 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.

plugins/google-ads-api-developer-assistant/commands/get-cids.md · 30 lines

What it actually says

Get CIDs Under MCC (/get-cids)

Retrieves the complete account hierarchy and child CIDs under a Google Ads Manager Account (MCC).

Instructions:

  1. Extract Parameters:

    • Extract the Manager Account ID (MCC) from $ARGUMENTS.
    • If not provided, check config/customer_id or prompt the user.
    • Resolve API version from config/api_version.txt.
  2. Execute Retrieval:

    • Run the hierarchy retrieval script:
      python3 skills/get-cids-under-mcc/scripts/get_cids_under_mcc.py --customer_id "<mcc_customer_id>" --api_version "<api_version>" --print_cids
      
    • If the user requested saving to CSV:
      python3 skills/get-cids-under-mcc/scripts/get_cids_under_mcc.py --customer_id "<mcc_customer_id>" --api_version "<api_version>" --save_csv
      
  3. Output Format:

    • Total number of child accounts found.
    • Hierarchical list with depth level, CID, descriptive name, and account type (client vs. sub-manager).
    • If saved to CSV, provide the file path in ~/saved/data/.
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.

  1. 2d ago First seen · 30 lines · 19 tokens per session scan A 86e24e7fc003

Subscribe to this mod's changes

get-cids 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 19 tokens to every session and 304 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.