analytics

A command for collecting production data from tools such as Google Search Console, Bing Webmaster, Clarity, Umami, Cloudflare, Stripe, and Google Analytics 4. It turns the findings into insights and actionable GitHub issues.

In plain words
What is it for?
Use it to inspect live-site performance, audit analytics, understand what is happening in production, and create GitHub issues from the results.
Why use it?
It brings website, search, infrastructure, payment, and business data into one review. This helps turn observed problems or opportunities into trackable development work.

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/rapiercraftstudios/forgedock/analytics
Clone the repo
git clone --depth 1 https://github.com/RapierCraftStudios/ForgeDock
Per session 75 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 11,524 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 2 findings. Scan, not verified.
Origin unknown 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.00075 $0.11524
Opus 5 $0.00037 $0.05762
Sonnet 5 $0.00015 $0.02305
Haiku 4.5 $0.00007 $0.01152

Measured 2d ago against content hash 965f8fbcf319, 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 2 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.

Reads MCP configurationlowAgent snooping

mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.

Agents MUST read this file for API keys, tokens, and login creds. Do NOT grep SOPS, do NOT hardcode tokens, do NOT look in `.mcp.json`.

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

token = requests.post(sa['token_uri'], data={'grant_type': 'urn:ietf:params:oauth:grant-type:jwt-bearer', 'assertion': signed}).json()['access_token']
commands/analytics.md · 863 lines

The source is not reproduced here

Licensed AGPL-3.0

The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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 · 863 lines · 75 tokens per session scan A 965f8fbcf319

Subscribe to this mod's changes

analytics is a command published in the GitHub repository RapierCraftStudios/ForgeDock (118 stars, last pushed 23d ago), licensed AGPL-3.0. It adds 75 tokens to every session and 11,524 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 2 findings (reads mcp configuration, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.