ai-traffic-tracking

ai-traffic-tracking is a skill for Claude Code from ariadoss/superskills. It costs 93 tokens per session (998 once invoked), scanned A, a copy of ai-traffic-tracking, MIT.

A guide to measuring visits that come from AI search tools such as ChatGPT, Perplexity, Gemini, Claude, or Copilot. It uses Google Analytics 4 and Google Search Console, which report website traffic and search performance.

In plain words
What is it for?
Setting up reports and filters for AI referrals, including traffic from AI search results and Google's AI Overviews.
Why use it?
AI-related visits may be grouped under referral, organic, or direct traffic, making them difficult to identify separately.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the superskills plugin — 197 skills shipped together

Good fit Setting up reports and filters for AI referrals, including traffic from AI search results and Google's AI Overviews.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ariadoss/superskills/ai-traffic
Install

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.

Any agent
npx skills add ariadoss/superskills --skill ai-traffic
Clone the repo
git clone --depth 1 https://github.com/ariadoss/superskills

Made for: Claude Code.

Or install superskills, the plugin that ships this one along with the rest of its 197 skills.

Wrote 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.

agentmods badge for ai-traffic-tracking

README.md
[![agentmods](https://agentmods.dev/badge/skills/ariadoss/superskills/ai-traffic/github.svg)](https://agentmods.dev/skills/ariadoss/superskills/ai-traffic)
Your own site
<a href="https://agentmods.dev/skills/ariadoss/superskills/ai-traffic"><img src="https://agentmods.dev/badge/skills/ariadoss/superskills/ai-traffic/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.

agentmods 80×15 button for ai-traffic-tracking

Your own site · 80×15
<a href="https://agentmods.dev/skills/ariadoss/superskills/ai-traffic"><img src="https://agentmods.dev/badge/skills/ariadoss/superskills/ai-traffic.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 93 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 998 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00093 $0.00998
Opus 5 $0.00046 $0.00499
Sonnet 5 $0.00019 $0.00200
Haiku 4.5 $0.00009 $0.00100

Measured 10d ago against content hash 3c9abc98eb7c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

ai-traffic-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 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.

Origin

This is a copy

100% identical to ai-traffic-tracking — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

marketing-skills/analytics/sources/ai-traffic/SKILL.md · 94 lines

How it starts

The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Analytics: AI Traffic

Guides tracking of AI-driven search traffic in Google Analytics 4 and Google Search Console.

When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.

Scope

  • AI search traffic: Track in GA4 and GSC; separate AI sources from organic referral
  • Google AI Overviews: AI summary box in Google search (formerly SGE)
  • AI-driven search: Traffic from ChatGPT, Perplexity, Gemini, Claude, Copilot, etc.

Why Track Separately

  • AI traffic is growing but GA4 often groups it as Referral, Organic, or Direct
  • AI visitors may have stronger intent and higher conversion
  • Separating AI Overviews from organic helps assess AI impact

Option 1: Exploration Report (Recommended)

  1. ExploreFree form
  2. Dimensions: Session source (or Session source / medium)
  3. Metrics: Sessions, Engagement rate, Event count, etc.
  4. Filters: Add filter →Session source Matches regex →use regex below
  5. Configure table, save report

Regex (common AI sources):

chatgpt\.com|openai\.com|openai|perplexity\.ai|perplexity|doubao\.com|chat\.qwen\.ai|copilot\.microsoft\.com|copilot\.com|(business\.)?gemini\.google|chat\.deepseek\.com|deepseek\.com|poe\.com|anthropic\.com|claude\.ai|bard\.google\.com|edgeservices\.bing\.com

Option 2: Custom Channel Group

  1. AdminData DisplayChannel Groups
  2. Copy default group, name e.g. "Default and AI Chatbots"
  3. Add channel "AI Chatbots": Source Matches regex (same regex)
  4. Important: Place "AI Chatbots" above "Referral" so it matches first
  5. Save and use in Traffic Acquisition

Option 3: Custom Report

  1. ReportsLibrary →Create Detail Report
  2. Use Traffic Acquisition template
  3. Add filter: Session source Matches regex (same regex)
  4. Save and add to menu

Read the full file on GitHub · 94 lines

Changes

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.

  1. 10d ago First seen · 94 lines · 93 tokens per session scan A 3c9abc98eb7c

Subscribe to this mod's changes

ai-traffic-tracking is a skill published in the GitHub repository ariadoss/superskills (9 stars, last pushed 3d ago), licensed MIT. It adds 93 tokens to every session and 998 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to ai-traffic-tracking, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens