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 agentmods add skills/jtrackingai/analytics-tracking-automation/tracking-syncnpx skills add jtrackingai/analytics-tracking-automation --skill tracking-syncgit clone --depth 1 https://github.com/jtrackingai/analytics-tracking-automationWrote 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/jtrackingai/analytics-tracking-automation/tracking-sync)<a href="https://agentmods.dev/skills/jtrackingai/analytics-tracking-automation/tracking-sync"><img src="https://agentmods.dev/badge/skills/jtrackingai/analytics-tracking-automation/tracking-sync.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 | $0.00027 | $0.00607 |
| Opus 5 | $0.00014 | $0.00303 |
| Sonnet 5 | $0.00005 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
tracking-sync 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 4d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tracking Sync
Use this skill for Step 4 and Step 5 work.
Inputs
One of:
- approved
<artifact-dir>/event-schema.json - existing
<artifact-dir>/gtm-config.json
Workflow
If the telemetry consent prompt appears and no prior choice is recorded, stop and follow ../../references/telemetry-consent.md before continuing.
If GTM config does not exist yet:
./event-tracking generate-gtm <artifact-dir>/event-schema.json --measurement-id <G-XXXXXXXXXX>
Then sync:
./event-tracking sync <artifact-dir>/gtm-config.json
If account/container/workspace IDs are already confirmed, skip interactive selection:
./event-tracking sync <artifact-dir>/gtm-config.json --account-id <account-id> --container-id <container-id> --workspace-id <workspace-id>
Hard Rules
- Do not bypass schema approval unless the user explicitly wants
--force. - Treat custom dimensions as a blocking checklist before sync/publish.
- Never auto-select GTM account, container, or workspace for the user.
synccalls Google's official GTM API via interactive OAuth. The consent flow needs outbound HTTP and a local loopback callback on127.0.0.1; runsyncin an environment that permits both.- Run
syncwith an interactive TTY from the start whenever it may prompt for OAuth consent, account, container, workspace, or new workspace name. Non-interactive invocation will fail at the first prompt. - Use non-interactive
synconly when exact--account-id,--container-id, and--workspace-idvalues are already confirmed.
Required Output
Produce and share:
<artifact-dir>/gtm-config.json<artifact-dir>/gtm-context.json<artifact-dir>/workflow-state.json
For Shopify runs, also expect:
<artifact-dir>/shopify-custom-pixel.js<artifact-dir>/shopify-install.md
Closeout Style
- default to a short answer-first sync summary before listing files
- summarize what was generated or synced, what still needs manual selection or approval, and any blocking checklist items first
- keep file listings and follow-up commands after the summary
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 81 lines · 27 tokens per session scan A 610ed37d11ac
tracking-sync is a skill published in the GitHub repository jtrackingai/analytics-tracking-automation (135 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 27 tokens to every session and 607 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.
Other skills, from other repositories
analytics
Use when instrumenting product or web analytics — GA4/PostHog SDK wiring, event taxonomy, funnels, double-counted events, consent gating, PII scrubbing. NOT charting that data (that is dashboard), NOT choosing which metrics matter (that is kpi-framework), NOT experiment math (that is ab-testing), NOT cookie-policy…
web-analytics
Analyze web traffic, SEO performance, and search engine trends using Google Search Console, Google Analytics 4, and Bing Webmaster Tools. Use when the user asks to analyze traffic, check SEO, or find keyword opportunities.
proxies
Oxylabs proxy networks: Residential, Mobile, shared Datacenter/ISP, and Dedicated Datacenter/ISP proxies with geo-targeting, IP rotation, session persistence, and port-based sticky IPs. Use when routing traffic through proxies, building scrapers with proxy auth, rotating or sticky sessions, whitelisting IPs, or…
karpathy-llm-wiki
Use when building or maintaining a personal LLM-powered knowledge base. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki quality, 'add to wiki', 'what do I know about', or any mention of 'LLM wiki' or 'Karpathy wiki'.
offer-compare-skill
Offer 对比决策器。用户同时拿到两份（或多份）offer 纠结怎么选时，扮演 Senior Career Decision Advisor：结构化对比 comp / 成长 / AI 敞口 / 公司强度 / 团队风险 / 晋升速度 / 生活方式，识别 front-loaded vs long-term upside、resume value、switch-out 难度、hidden risks，最后给一条明确、有立场、不中性的推荐（并附「你是 X 类人选 A，你是 Y 类人选 B」的分叉判定）。三步：贴两份 offer → 补 priorities & 现状 → 自动生成并打开一份 HTML Offer Decision…
bot-traffic-detection
Identify and exclude bot, scraper, and spam sessions from GA4 data.