analytics

A command-line tool for viewing website and API analytics, meaning measurements about visitors, traffic, performance, and usage.

In plain words
What is it for?
Use it to view overviews, traffic by pages or countries, conversion funnels, real-user loading metrics, AI crawler activity, API requests and errors, route performance, and API callers.
Why use it?
It gathers common reports in one interface, so you can investigate how people and automated agents use a project and where its APIs receive traffic.

Command

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.

agentmods
npx agentmods add commands/gotempsh/temps/analytics
Clone the repo
git clone --depth 1 https://github.com/gotempsh/temps
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,579 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.03579
Opus 5 $0.00000 $0.01790
Sonnet 5 $0.00000 $0.00716
Haiku 4.5 $0.00000 $0.00358

Measured 2d ago against content hash 303f2c9f09de, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 2d 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.

skills/temps/references/commands/analytics.md · 252 lines

How it starts

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

analytics command reference

Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.

analytics (alias: stats)

View project analytics

Subcommands:

  • overview (o) - Show analytics dashboard overview
  • top - Show breakdown by dimension: pages, referrers, browsers, os, devices, countries, regions, cities, channels, events, languages, utm_source, utm_medium, utm_campaign
  • funnels - Show funnel conversion metrics for all funnels
  • performance (speed) - Show real-user Web Vitals and optional dimension breakdowns
  • ai-agents - Show AI crawler / provider breakdown (web /analytics/ai-agents)
  • ai-pages - Show pages crawled by AI agents, with distinct-agent counts
  • ai-page - Show which agents/providers crawled a single page (e.g. /docs)
  • api-overview - Show API traffic timeseries (requests, errors, latency) from /api-analytics/timeseries
  • api-routes - Show top API routes by request count from /api-analytics/routes
  • api-callers - Show top API callers by client IP from /api-analytics/callers
  • api-ip - Show routes called by one client IP with latency and error analytics
  • api-path - Show client IPs calling one path with latency and error analytics
  • api-query - Run a typed multi-dimensional API traffic aggregation
  • api-summary - Show an AI-generated summary of API traffic from /api-analytics/summary (requires AI Assistance to be configured and enabled on the project)

analytics overview (alias: o)

Show analytics dashboard overview

Options:

Flag Description Default Required
-p, --project <project> Project slug or ID - No
--period <period> Time period: today, h, d, m (e.g. 1h, 6h, 48h, 7d, 30d, 3m) 24h No
--json Output in JSON format - No

analytics top

Read the full file on GitHub · 252 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. 2d ago First seen · 252 lines · 0 tokens per session scan A 303f2c9f09de

Subscribe to this mod's changes

analytics is a command published in the GitHub repository gotempsh/temps (700 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,579 tokens. 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.