agent-traffic-analytics

agent-traffic-analytics is a skill for Codex from apostl-dev/apostl-skills. It costs 102 tokens per session (2,940 once invoked), scanned A, original, MIT.

A workflow for adding server-side analytics that estimates visits from AI agents to public websites, documentation, APIs, and related pages. It can use a Cloudflare Worker or a server software library.

In plain words
What is it for?
Use it to install and verify collection, review estimated agent visits, and see request counts and popular pages.
Why use it?
It shows which public pages receive agent traffic without sending request bodies, cookies, authorization headers, or query parameters.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: mentions Codex.

Good fit Use it to install and verify collection, review estimated agent visits, and see request counts and popular pages.

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

Made for: 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 agent-traffic-analytics

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/apostl-dev/apostl-skills/agent-traffic-analytics"><img src="https://agentmods.dev/badge/skills/apostl-dev/apostl-skills/agent-traffic-analytics.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 102 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,940 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 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.00102 $0.02940
Opus 5 $0.00051 $0.01470
Sonnet 5 $0.00020 $0.00588
Haiku 4.5 $0.00010 $0.00294

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

Security

Grade A, and why

agent-traffic-analytics 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.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/pulse_setup.py, tests/test_pulse_setup.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/agent-traffic-analytics/SKILL.md · 279 lines

How it starts

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

Agent Traffic Analytics

Answer one question with inspectable server-side evidence: how many estimated AI agents are using this public product right now, and which pages do they use?

Contract

Pulse measures eligible public page requests. The selected server-side collector sends the request IP address, full User-Agent, and canonical page identity as origin + pathname. It strips query strings, fragments, and URL credentials. It never sends request bodies, cookies, authorization headers, or query parameters.

The server SDK counts public GET and HEAD responses with status 2xx through 4xx. It excludes common static assets, health checks, auth/private paths, and mutations by default. Apostl performs traffic classification in the analytics layer; do not configure a service type in application code.

The dashboard's Top Pages view covers 30 days and shows estimated unique agents plus request count for each canonical page. Classification and agent counts are heuristic estimates; IP address plus User-Agent cannot prove a unique person, agent, model, or organization. Read pulse-contract.md before changing collection, verification, identity, or claim behavior.

Fit and payoff

Use Pulse for server-rendered SaaS sites, developer docs, agent-native products, public API surfaces, Markdown, and llms.txt. The owner gets a live 30-minute agent estimate, a 30-day page ranking, and inspectable proof that the deployed middleware produced a real event. For an existing Express or Next.js server, the code change is one client plus one middleware or handler wrapper; budget about ten minutes for the code edit, then add whatever test, review, and deploy time the target normally requires. Do not promise a live dashboard before the public verification request and its event both pass.

Starting requires a public HTTPS origin, authority over its serving code and secret runtime, and an authorized deploy path. The server SDK additionally requires permission to install a package; the Cloudflare path requires authority over the exact hostname and matching Worker route. A human account is not required until claim; the owner then uses Google, GitHub, or an email magic link.

Read the full file on GitHub · 279 lines

Files

What ships with it

5 files 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.

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 · 279 lines · 102 tokens per session scan A 5ebbd611e4a5

Subscribe to this mod's changes

agent-traffic-analytics is a skill published in the GitHub repository apostl-dev/apostl-skills (2 stars, last pushed 9d ago), licensed MIT. It adds 102 tokens to every session and 2,940 once invoked, about $0.0005 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-31.