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.
npx skills add TrueClicks/claude-plugins --skill skill-108-cross-device-conversion-trackinggit clone --depth 1 https://github.com/TrueClicks/claude-pluginsWrote 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/skills/trueclicks/claude-plugins/skill-108-cross-device-conversion-tracking)<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-108-cross-device-conversion-tracking"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-108-cross-device-conversion-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/skills/trueclicks/claude-plugins/skill-108-cross-device-conversion-tracking"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-108-cross-device-conversion-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.00023 | $0.00505 |
| Opus 5.5 | $0.00009 | $0.00202 |
| Sonnet 5.5 | $0.00005 | $0.00101 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
skill-108-cross-device-conversion-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 21d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill 108: Cross-Device Conversion Tracking
Purpose
Evaluate whether cross-device conversion paths are captured. Multi-device journeys are the norm; single-device attribution undervalues initiating campaigns and causes budget misallocation.
Data Requirements
Data Source: Standard + Custom GAQL
Standard Data:
data/account/account_summary.md- Enhanced Conversions statusdata/account/conversion_actions.md- Conversion settings
Reference GAQL:
SELECT
segments.device,
segments.conversion_action_name,
metrics.conversions,
metrics.all_conversions
FROM campaign
WHERE segments.date DURING LAST_30_DAYS
Use /google-ads:get-custom for device-level conversion analysis.
Analysis Steps
- Assess Tracking Capability: Check Google Signals, Enhanced Conversions, User-ID status
- Review Enhanced Conversions Status: Identify which conversions have enhanced tracking
- Analyze Cross-Device Patterns: Compare mobile vs. desktop conversion rates
- Evaluate Attribution Settings: Check if DDA and cross-device conversions enabled
Thresholds
| Condition | Severity |
|---|---|
| Enhanced Conversions not enabled | Critical |
| Large gap between conversions and all_conversions | Warning |
| Mobile bid adjustments heavily negative (compensating) | Warning |
| Last-click attribution still in use | Warning |
| Google Signals disabled | Info |
Output
Short (default):
## Cross-Device Tracking Audit
**Account:** [name] | **Enhanced Conv:** [On/Off] | **DDA:** [On/Off] | **Issues:** [count]
### Critical
- **Enhanced Conversions not enabled** - Missing cross-device paths
### Warnings
- **Mobile -50% bid adjustment** - May be compensating for tracking gap
- **Last-click attribution** - Undervalues mobile/initiating touchpoints
### Recommendations
1. Enable Enhanced Conversions for web
2. Switch to Data-Driven Attribution
3. Review mobile bid adjustments after cross-device tracking enabled
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.
- 21d ago First seen · 73 lines · 23 tokens per session scan A 26645fd108ca
skill-108-cross-device-conversion-tracking is a skill published in the GitHub repository TrueClicks/claude-plugins (2 stars, last pushed 22d ago), licensed MIT. It adds 23 tokens to every session and 505 once invoked, about $0.0001 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-10-08.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…