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.
git clone --depth 1 https://github.com/Ad-Superpowers/ad-superpowers-pluginWrote 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/commands/ad-superpowers/ad-superpowers-plugin/gtm-container-audit)<a href="https://agentmods.dev/commands/ad-superpowers/ad-superpowers-plugin/gtm-container-audit"><img src="https://agentmods.dev/badge/commands/ad-superpowers/ad-superpowers-plugin/gtm-container-audit.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.1 | $0.00041 | $0.01462 |
| Opus 5 | $0.00020 | $0.00731 |
| Sonnet 5 | $0.00008 | $0.00292 |
| Haiku 4.5 | $0.00004 | $0.00146 |
Grade A, and why
gtm-container-audit 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Platforms: google_tag_manager Tier: pro
This command requires the Ad Superpowers MCP connector to access your ad account data. Connect at https://app.adsuperpowers.ai if you haven't already.
GTM Container Audit
Audit Google Tag Manager containers for issues, health scoring, and prioritized remediation.
- Container: all
- Focus: all
OUTPUT FORMAT (CRITICAL - follow this EXACT structure)
Health Score: [N]/100 -- [Excellent/Good/Fair/Poor/Critical]
Score bands: 90-100 Excellent | 75-89 Good | 60-74 Fair | 40-59 Poor | <40 Critical
Summary
| Metric | Count |
|---|---|
| Active Tags | N |
| Paused Tags | N |
| Triggers | N (N unused) |
| Custom Variables | N |
| Built-in Variables | N |
| Workspaces | N |
Category Scores
| Category | Score | Weight | Weighted |
|---|---|---|---|
| Tag Health | N/100 | 30% | N |
| Trigger Health | N/100 | 25% | N |
| Variable Health | N/100 | 20% | N |
| Workspace Health | N/100 | 15% | N |
| Governance | N/100 | 10% | N |
| Overall | N/100 |
Critical Issues (fix immediately)
| # | Issue | Tag/Trigger | Impact | Fix |
|---|
High Priority (fix within 7 days)
| # | Issue | Tag/Trigger | Impact | Fix |
|---|
Consent Compliance
| Metric | Value |
|---|---|
| Marketing/Ad tags | N |
| With consent gate | N |
| At risk (no consent) | N |
| Tags at risk: [list tag names firing without consent check] |
Tag Inventory
| Tag Name | Type | Trigger | Status | Issue |
|---|
Remediation Roadmap
Week 1 (Critical): [actions] Week 2 (High): [actions] Month 1 (Medium): [actions] Estimated effort: X hours
EXECUTION STEPS
Step 1: Discover containers
Conditional: if container_id == "all" or not container_id
gtm_list_containers()
List all containers. Present container names and IDs. Proceed to audit each (or ask user to pick one if many).
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.
- 7d ago First seen · 162 lines · 41 tokens per session scan A 533f1592bc1e
gtm-container-audit is a command published in the GitHub repository Ad-Superpowers/ad-superpowers-plugin (5 stars, last pushed 9d ago), licensed MIT. It adds 41 tokens to every session and 1,462 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-08-31.
Other commands, from other repositories
meta-audit
Full Meta Ads account audit, tailored to ecommerce or lead-gen automatically.
setup
First-run setup for the ga-mcp-full MCP server — install the CLI if needed, then complete the browser login.
logout
Google Ads command — logout.
status
Google Ads command — status.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.