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 Goodsmileduck/claude-registry --skill cloudflare-analyticsgit clone --depth 1 https://github.com/Goodsmileduck/claude-registryWrote 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/goodsmileduck/claude-registry/cloudflare-analytics)<a href="https://agentmods.dev/skills/goodsmileduck/claude-registry/cloudflare-analytics"><img src="https://agentmods.dev/badge/skills/goodsmileduck/claude-registry/cloudflare-analytics.svg" alt="Measured on agentmods" 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.00097 | $0.01093 |
| Opus 5 | $0.00048 | $0.00547 |
| Sonnet 5 | $0.00019 | $0.00219 |
| Haiku 4.5 | $0.00010 | $0.00109 |
Grade A, and why
cloudflare-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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloudflare Analytics
Cloudflare's MCP servers do not expose traffic analytics — the observability
server covers Workers Logs only (and only when a Worker sets [observability]
in its wrangler config), and Radar is public internet-wide data unrelated to any
one account. Per-hostname numbers come from the GraphQL Analytics API, which
these scripts wrap.
Setup
All scripts need CLOUDFLARE_API_TOKEN. Create at dash.cloudflare.com → My
Profile → API Tokens → Custom token with Zone > Analytics > Read,
Zone > Zone > Read, and Account > Account Analytics > Read.
Never let the user paste the token into the conversation — it lands in the
transcript permanently. Ask them to run the command themselves (in Claude Code,
prefixed with !), which returns only the output. If a token does end up in the
transcript, say so plainly and tell them to rotate it.
Workflow
1. Probe limits first. Plan entitlements decide what is answerable, and they are not derivable from the docs — the published API capability is not the same as a given zone's grant.
scripts/cf-limits.sh <zone-name>
Returns maxDuration (widest single window) and notOlderThan (retention) per
dataset. These are independent: 8-day retention with a 1-day max window means
eight separate queries, not one.
2. Pick the dataset by whether you need a per-hostname breakdown.
clientRequestHTTPHost exists only on httpRequestsAdaptiveGroups, which is
the most range-restricted dataset. That tension drives most decisions here —
see references/datasets.md.
3. Run.
scripts/cf-host-traffic.sh <zone> [YYYY-MM-DD] # per-hostname table, 24h window
scripts/cf-query.sh <query-file> '<vars-json>' # arbitrary query
cf-query.sh accepts - to read the query from stdin, prints raw JSON, and
exits non-zero on GraphQL errors.
Non-obvious behavior
Errors arrive with HTTP 200. A failed query returns status 200 with an
errors array. Always inspect body.errors; both scripts do.
What ships with it
4 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.
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.
- 7d ago First seen · 98 lines · 97 tokens per session scan A 0675d690ace6
cloudflare-analytics is a skill published in the GitHub repository Goodsmileduck/claude-registry (1 stars, last pushed 1mo ago), licensed MIT. It adds 97 tokens to every session and 1,093 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.
Other skills, from other repositories
cicd-expert
Expert-level CI/CD with GitHub Actions, Jenkins, deployment pipelines, and automation. Use when the user mentions CI/CD, GitHub Actions, Jenkins, GitLab CI, deployment, or automation, or when the task involves CI/CD Fundamentals, Pipeline Design, Workflow Basics, or Docker Build and Push.
cicd-agent
CI/CD pipeline design and review — GitHub Actions, pipeline best practices, secrets management, deployment strategies, and release automation.
devops-best-practices
Opinionated production-grade DevOps defaults for Terraform, Kubernetes, CI/CD, Docker, cloud security, observability, cost, and disaster recovery. ALWAYS use when generating, reviewing, or modifying any infrastructure code, Kubernetes manifests (Deployment, Service, StatefulSet, Helm, Kustomize), Terraform (.tf…
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
mcporter
List, auth, and call MCP servers/tools from the terminal.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.