Menu

Individual skill

mcc-hack-audit

0upvotes

Portfolio-wide scan of every manager (MCC) that has access to accounts in your Google Ads tree. Built after an MCC link-fraud incident where hostile external MCCs were found linked to client accounts via compromised admin credentials. Classifies each manager link as INTERNAL (in your tree), HOSTILE (known threat), or EXTERNAL (potential exposure — no judgment). Outputs CSV by default with optional Google Sheets upload. Auto-invoke when user says 'mcc hack audit', 'audit mcc links', 'scan for external managers', 'check manager links', 'run mcc link scan', 'find external mccs', or asks who has access to their Google Ads accounts.

mcc-hack-audit/SKILL.md

Read pinned source

Source commit 90f0e419f2d820789d5e50eee1237ab9fd14dfc6

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
80
Repository last updated
Aug 25, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# MCC Hack Audit

Owns one workflow: walk your entire Google Ads tree and map every manager
(MCC) with a link into it — then hand the operator a triage-ready answer to
**"which MCCs currently have access to which of my accounts, and which are
outside my own tree?"** Built after a real-world MCC link-fraud incident
where hostile external MCCs gained access to client accounts via compromised
client-side admin credentials.

The triage judgment — which links matter, when a finding becomes an incident,
what "trusted" costs — is [`rules.md`](rules.md). The exact
walk/classification/output mechanics and the hard-won API limitations are
[`references/scan-contract.md`](references/scan-contract.md).
Back to top