traffic-analysis

traffic-analysis is a skill for Claude Code from ariadoss/superskills. It costs 53 tokens per session (1,772 once invoked), scanned A, a copy of traffic-analysis, MIT.

A guide to analyzing where website visits come from, including search, paid ads, social media, referrals, email, and direct visits. It also covers dark traffic, visits whose original source is not recorded, and UTM tags used to label campaigns.

In plain words
What is it for?
Use it to analyze traffic sources, investigate direct or unattributed visits, improve campaign tagging, compare branded and non-branded search traffic, and separate bots from people.
Why use it?
It helps distinguish real acquisition channels from visits that are incorrectly or incompletely attributed. It also provides a way to organize traffic reports and account for automated bot visits.

Skill for Claude Code

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

Part of the superskills-marketing plugin — 161 skills shipped together

Good fit Use it to analyze traffic sources, investigate direct or unattributed visits, improve campaign tagging, compare branded and non-branded search traffic, and separate bots from people.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ariadoss/superskills/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 traffic
Clone the repo
git clone --depth 1 https://github.com/ariadoss/superskills

Made for: Claude Code.

Or install superskills-marketing, the plugin that ships this one along with the rest of its 161 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 traffic-analysis

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/ariadoss/superskills/traffic"><img src="https://agentmods.dev/badge/skills/ariadoss/superskills/traffic.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,772 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.00053 $0.01772
Opus 5.5 $0.00021 $0.00709
Sonnet 5.5 $0.00011 $0.00354
Haiku 4.5 $0.00005 $0.00177

Measured 1mo ago against content hash 5ba4ecf1f5b2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

traffic-analysis 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 1mo 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 traffic-analysis — 155 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/traffic/SKILL.md · 157 lines

How it starts

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

Analytics: Traffic

Guides website traffic analysis across all channels (organic, paid, social, referral, direct). Covers traffic source attribution, dark traffic identification, and multi-channel reporting.

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

  • Traffic sources: Organic, paid, social, referral, direct, email
  • Dark traffic: Unattributed visits labeled as "Direct / None"
  • Attribution: UTM tagging, segmenting, reporting accuracy

Branded vs. Non-Branded Traffic (Organic)

Type Characteristics
Branded Higher CTR, conversion, purchase intent; users closer to funnel bottom
Non-branded Touchpoint with future users; most sites get more non-brand traffic; competition fiercer

Brand traffic grows over time as brand awareness increases.

Bot Traffic

A large share of traffic can be bot traffic—RPA, search crawlers, spiders, scrapers. Exclude or segment when evaluating real user behavior; use GA4 filters or segments to isolate human traffic.

Traffic Channels

Channel Typical Sources Attribution
Organic Google, Bing, other search Referrer preserved
Paid (web) Google Ads, Meta Ads, etc. UTM required
Paid (app) App install ads; Google App Campaigns, Apple Search Ads UTM; in-app events
Paid (TV/CTV) Streaming ads; Hulu, Roku, YouTube TV UTM for QR/URL; brand lift
Social Public posts (Facebook, LinkedIn, etc.) Often preserved
Referral External sites, backlinks Referrer preserved
Direct Typed URL, bookmarks No referrer
Email Newsletters, campaigns Often dark without UTM

Dark Traffic

What It Is

Traffic without clear origin--analytics tools default to "Direct" when referrer is missing. Common causes:

Read the full file on GitHub · 157 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. 1mo ago Changed · -36 tokens per session 5ba4ecf1f5b2
  2. 1mo ago First seen · 157 lines · 89 tokens per session scan A 7a3be7d3b923

Subscribe to this mod's changes

traffic-analysis is a skill published in the GitHub repository ariadoss/superskills (12 stars, last pushed 2d ago), licensed MIT. It adds 53 tokens to every session and 1,772 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to traffic-analysis, differing in 155 lines, and is treated as a copy.

Related

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…

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

systematic-debugging

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

obra/superpowers · 21 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

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 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