Borrowing it
Nothing to install: this file belongs to kLOsk/adloop. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kLOsk/adloop/main/.claude/commands/diagnose-tracking.mdgit clone --depth 1 https://github.com/kLOsk/adloopWrote 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/klosk/adloop/diagnose-tracking)<a href="https://agentmods.dev/commands/klosk/adloop/diagnose-tracking"><img src="https://agentmods.dev/badge/commands/klosk/adloop/diagnose-tracking/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.
<a href="https://agentmods.dev/commands/klosk/adloop/diagnose-tracking"><img src="https://agentmods.dev/badge/commands/klosk/adloop/diagnose-tracking.svg" alt="Reviewed on agentmods" width="80" 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.00012 | $0.00396 |
| Opus 5.5 | $0.00005 | $0.00158 |
| Sonnet 5.5 | $0.00002 | $0.00079 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
diagnose-tracking 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 2mo 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.
What it actually says
Diagnose tracking and conversion issues for: $ARGUMENTS
1. GDPR check first
Before investigating anything technical, consider:
- Are Ads clicks > GA4 sessions? This is likely GDPR consent rejection (normal in EU, 2:1 to 5:1 ratio)
- State this upfront before deeper investigation
2. Attribution check
- Run
attribution_checkwith relevantconversion_events(e.g., sign_up, purchase, form_submit) - Review the
insights[]— the tool already factors in GDPR consent gaps - Only proceed to deeper investigation if insights suggest a real tracking problem
3. Codebase analysis
- Search for
gtag('event'anddataLayer.push({event:to find tracking code - Search for
gtag('consent'to check Consent Mode v2 implementation - Extract all event names from code
4. Validate tracking
- Run
validate_trackingwith the extracted event names - Compare results: matched (working), missing (in code but not firing), unexpected (in GA4 but not in code)
- Missing events = code not deployed or behind untriggered conditions
- Unexpected events = likely from tag managers
5. Landing page check
- Run
landing_page_analysisto check pages with traffic but zero conversions - If codebase is accessible, read flagged pages for UX issues
6. Diagnosis
- Only diagnose tracking as BROKEN when discrepancy can't be explained by consent
- Signs of real issues: zero sessions for ALL sources, organic also anomalous, events in code but never fire
- If tracking code needs to be added, use
generate_tracking_codeto produce the snippet
Present unified diagnosis: GDPR impact + tracking status + specific recommendations.
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.
- 2mo ago First seen · 45 lines · 12 tokens per session scan A 5f07c7cbb6b2
diagnose-tracking is a command published in the GitHub repository kLOsk/adloop (293 stars, last pushed 2d ago), licensed MIT. It adds 12 tokens to every session and 396 once invoked, about $0.0000 per session on Opus 5.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.
diagnose-tracking compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| diagnose-trackingkLOsk/adloop | Command | 293 | 2d ago | MIT | A | 12 | Claude Code |
| seo-auditbsisduck/google-search-ads-analytics-docs | Command | 2 | 5mo ago | none | A | 33 | Claude Code |
| google-docsbsisduck/google-search-ads-analytics-docs | Command | 2 | 5mo ago | none | A | 31 | Claude Code |
| setupringo380/ga-mcp-full | Command | 0 | 27d ago | MIT | A | 24 | Claude Code |
| auth-statusringo380/ga-mcp-full | Command | 0 | 27d ago | MIT | A | 16 | Claude Code |
| auth-logoutringo380/ga-mcp-full | Command | 0 | 27d ago | MIT | A | 15 | Claude Code |
| reconnectringo380/ga-mcp-full | Command | 0 | 27d ago | MIT | B | 40 | Claude Code |