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 jtrackingai/analytics-tracking-automation --skill tracking-live-gtmgit 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-live-gtm)<a href="https://agentmods.dev/skills/jtrackingai/analytics-tracking-automation/tracking-live-gtm"><img src="https://agentmods.dev/badge/skills/jtrackingai/analytics-tracking-automation/tracking-live-gtm/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/jtrackingai/analytics-tracking-automation/tracking-live-gtm"><img src="https://agentmods.dev/badge/skills/jtrackingai/analytics-tracking-automation/tracking-live-gtm.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.00030 | $0.00603 |
| Opus 5 | $0.00015 | $0.00302 |
| Sonnet 5 | $0.00006 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
tracking-live-gtm 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 10d 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 Live GTM
Use this skill to audit the site's real live GTM setup before event generation.
Inputs
One of:
- confirmed
<artifact-dir>/site-analysis.json - explicit live GTM public IDs when the crawl did not capture them
Workflow
If the telemetry consent prompt appears and no prior choice is recorded, stop and follow ../../references/telemetry-consent.md before continuing.
Run the live baseline step before schema preparation whenever the site has a real GTM container installed:
./event-tracking analyze-live-gtm <artifact-dir>/site-analysis.json
If multiple live containers matter and the user already knows the primary comparison target:
./event-tracking analyze-live-gtm <artifact-dir>/site-analysis.json --primary-container-id GTM-XXXXXXX
If the user wants to test the quality of the already-published live GTM setup on the real site, run:
./event-tracking verify-live-gtm <artifact-dir>/site-analysis.json
During review:
- show all detected live GTM containers
- explain which container is the primary comparison baseline
- summarize existing live events, measurement IDs, and obvious issues
- when
verify-live-gtmwas run, separate parsed live definitions from browser-verified live firing evidence - if this review is part of
tracking_health_audit, clearly separate runtime-detected live definitions from any formal preview-verified automation evidence - stop before schema authoring if the user wants to review the live baseline first
Required Output
Produce and share:
<artifact-dir>/live-gtm-analysis.json<artifact-dir>/live-gtm-review.md- optional
<artifact-dir>/live-preview-result.json - optional
<artifact-dir>/live-preview-report.md - optional
<artifact-dir>/live-tracking-health.json - updated
<artifact-dir>/workflow-state.json
Closeout Style
- default to a compact live-tracking summary before listing files
- name the detected live events directly instead of only reporting event counts
- in
tracking_health_audit, explicitly separate runtime-detected live definitions from formal preview-verified automation evidence - list artifacts only after the decision-ready 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.
- 10d ago First seen · 81 lines · 30 tokens per session scan A d4d4de1923a7
tracking-live-gtm is a skill published in the GitHub repository jtrackingai/analytics-tracking-automation (136 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 603 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-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.
short-drama
A production workflow for making multi-episode AI short dramas, covering story planning, character consistency, scripts, generated video shots, voices, sound, subtitles, and final assembly.
chart-visualization
A chart-making tool that turns data into a single static chart image, such as a bar, line, pie, scatter, radar, flow, or mind-map chart.
multi-voice-dubbing
A script-to-audio workflow that gives different characters different voices and emotions, then combines their lines into one audio track with subtitles naming each speaker.
skill-topic-evaluator
A topic-evaluation tool that scores one proposed content idea across audience interest, account fit, competition, timing, revenue potential, effort, and compliance risk.