traffic-analyzer

traffic-analyzer is a skill for Claude Code, Codex from Affitor/affiliate-skills. It costs 164 tokens per session (3,665 once invoked), scanned A, original, MIT.

A website-traffic analysis tool for studying a domain’s visitors, popularity, engagement, and traffic sources. A domain is a website address such as example.com.

In plain words
What is it for?
Use it to evaluate affiliate websites, compare competitors or affiliate programs, investigate audience sources, and assess a niche.
Why use it?
It helps assess whether an advertiser or competitor’s website has a real audience instead of relying only on claims.

Skill for Claude CodeCodex

Which agent this was written for is unclear — built for openclaw. Also seen: mentions Claude Code; built for openclaw; mentions Gemini CLI.

Good fit Use it to evaluate affiliate websites, compare competitors or affiliate programs, investigate audience sources, and assess a niche.

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

Made for: Claude Code, Codex.

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-analyzer

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/affitor/affiliate-skills/traffic-analyzer"><img src="https://agentmods.dev/badge/skills/affitor/affiliate-skills/traffic-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 164 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,665 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found 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.00164 $0.03665
Opus 5 $0.00082 $0.01833
Sonnet 5 $0.00033 $0.00733
Haiku 4.5 $0.00016 $0.00366

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

Security

Grade A, and why

traffic-analyzer 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 9d 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

Copies of this mod

1 near-identical copy found in the catalogue:

skills/research/traffic-analyzer/SKILL.md · 357 lines

How it starts

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

Traffic Analyzer

Analyze website traffic, engagement, and traffic sources for any domain. Goes beyond raw data — scores the domain, interprets what the traffic patterns mean for affiliate promotion, and recommends whether the program is worth your time.

A tool returns numbers. This skill returns a verdict.

Use cases:

  • Is this affiliate program's website healthy? (High traffic = more brand awareness = easier conversions)
  • Where does a competitor get their traffic? (Find channels they're ignoring)
  • Compare 2-3 affiliate programs by advertiser website strength
  • Validate a niche by checking traffic to the top programs in it

Stage

This skill belongs to Stage S1: Research

When to Use

  • Before committing to promote an affiliate program — check if the advertiser is legit
  • When comparing multiple programs — traffic is a proxy for brand strength
  • When competitor-spy identifies competitor sites — analyze their traffic sources
  • When evaluating a niche — check if the top programs have healthy traffic
  • When an advertiser claims "millions of users" — verify with data

Input Schema

domains: string[]             # (required) 1-5 domains to analyze — "heygen.com", "synthesia.io"
compare: boolean              # (optional, default: true if 2+ domains) Side-by-side comparison
focus: string                 # (optional, default: "affiliate") 
                              # "affiliate" — score from promoter perspective
                              # "competitor" — analyze as a competitor site
                              # "advertiser" — evaluate advertiser health

Workflow

Step 1: Gather Traffic Data

With SimilarWeb API (see shared/references/social-data-providers.md):

If social_data_config.similarweb is configured:

  • Call SimilarWeb API for each domain
  • Returns: global rank, country rank, visits, pages/visit, avg duration, bounce rate, traffic sources

Without API (web_search fallback):

For each domain:

  1. web_search "[domain] traffic similarweb" → often shows rank and visit estimates in snippets
  2. web_search "[domain] site traffic statistics" → third-party reports
  3. web_search "site:[domain]" → Google index count as proxy for content depth
  4. web_search "[domain] alexa rank" OR "[domain] semrush traffic" → alternative sources
  5. web_fetch "https://www.similarweb.com/website/[domain]/" → extract visible data from SimilarWeb free page (may be limited)

Read the full file on GitHub · 357 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. 9d ago First seen · 357 lines · 164 tokens per session scan A f8e353290113

Subscribe to this mod's changes

traffic-analyzer is a skill published in the GitHub repository Affitor/affiliate-skills (652 stars, last pushed 3d ago), licensed MIT. It adds 164 tokens to every session and 3,665 once invoked, about $0.0008 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.

Related

Other skills, from other repositories