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 gabrielmoreira/agent-skills-mirror --skill traffic-analyzergit clone --depth 1 https://github.com/gabrielmoreira/agent-skills-mirrorWrote 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/gabrielmoreira/agent-skills-mirror/traffic-analyzer)<a href="https://agentmods.dev/skills/gabrielmoreira/agent-skills-mirror/traffic-analyzer"><img src="https://agentmods.dev/badge/skills/gabrielmoreira/agent-skills-mirror/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.
<a href="https://agentmods.dev/skills/gabrielmoreira/agent-skills-mirror/traffic-analyzer"><img src="https://agentmods.dev/badge/skills/gabrielmoreira/agent-skills-mirror/traffic-analyzer.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.00164 | $0.03665 |
| Opus 5.5 | $0.00066 | $0.01466 |
| Sonnet 5.5 | $0.00033 | $0.00733 |
| Haiku 4.5 | $0.00016 | $0.00366 |
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 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.
This is a copy
100% identical to traffic-analyzer — 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.
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-spyidentifies 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:
web_search "[domain] traffic similarweb"→ often shows rank and visit estimates in snippetsweb_search "[domain] site traffic statistics"→ third-party reportsweb_search "site:[domain]"→ Google index count as proxy for content depthweb_search "[domain] alexa rank"OR"[domain] semrush traffic"→ alternative sourcesweb_fetch "https://www.similarweb.com/website/[domain]/"→ extract visible data from SimilarWeb free page (may be limited)
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.
- 1mo ago First seen · 357 lines · 164 tokens per session scan A f8e353290113
traffic-analyzer is a skill published in the GitHub repository gabrielmoreira/agent-skills-mirror (19 stars, last pushed today), licensed MIT. It adds 164 tokens to every session and 3,665 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to traffic-analyzer, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
traffic-analyzer
Analyze website traffic, global rank, engagement metrics, and traffic sources for any domain. Use this skill to evaluate affiliate program websites, compare competitor traffic, assess advertiser strength, or understand where an audience comes from. Triggers on: "analyze traffic for [domain]", "how much traffic does…
mirrord-prev-env
Help users create and manage mirrord preview environments — running a modified service as an isolated pod in a shared Kubernetes cluster, scoped by an environment key and HTTP/queue traffic filtering, so teams can validate and review changes against real traffic without affecting live services. Use when a developer…
mirrord-kafka
Helps DevOps engineers configure mirrord Operator's Kafka queue splitting feature end-to-end. Generates the MirrordSplitConfig and MirrordPropertyList Kubernetes CRD YAMLs (the current resources; MirrordKafkaTopicsConsumer + MirrordKafkaClientConfig are deprecated but still supported), the matching mirrord.json…
mirrord-operator
Help users install and configure the mirrord Operator for team/enterprise environments. Use when users ask about operator setup, Helm installation, cloud API key or license configuration, air-gapped/offline licensing, enabling features (queue splitting, DB branching, preview environments, multi-cluster), internal…
mirrord-up
Helps users run multiple concurrent mirrord sessions from a single mirrord-up.yaml (compose-style multi-service local debugging). Use when the user mentions mirrord up, mirrord-up.yaml, mirrord up init, debugging several related microservices together, or managing multiple mirrord sessions' lifecycle in one command.
mirrord-chaos
Help users chaos test their app with mirrord: inject artificial latency or connection errors into a mirrord session's outgoing traffic via per-session chaos rules managed with the mirrord chaos CLI. Use when a user wants to add latency or delay to outgoing connections or a dependency (e.g. a slow database), simulate…