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-workersgit 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-workers)<a href="https://agentmods.dev/skills/goodsmileduck/claude-registry/cloudflare-workers"><img src="https://agentmods.dev/badge/skills/goodsmileduck/claude-registry/cloudflare-workers/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/goodsmileduck/claude-registry/cloudflare-workers"><img src="https://agentmods.dev/badge/skills/goodsmileduck/claude-registry/cloudflare-workers.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.00163 | $0.02327 |
| Opus 5.5 | $0.00065 | $0.00931 |
| Sonnet 5.5 | $0.00033 | $0.00465 |
| Haiku 4.5 | $0.00016 | $0.00233 |
Grade A, and why
cloudflare-workers scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
6. **Module syntax only.** Service Worker syntax (`addEventListener('fetch', ...)`) is deprecated. New `compatibility_date` values can refuse it. Use `export default { fetch(req, env, ctx) { ... } }`. How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloudflare Workers
When to invoke
Symptoms:
- A binding works in
wrangler devbut isundefinedin production. wrangler deployfails withCannot apply new-class migration to class 'X' that is already depended on by existing Durable ObjectsorClass 'X' cannot be used as a Durable Objectafter a code rename.- A secret value is visible in the Cloudflare dashboard under "Variables" — or worse, committed in
wrangler.toml. - Same hostname has both a Custom Domain and a route pattern, and routing is non-deterministic.
- New Pages project — should it actually be a Worker?
- Two Workers in the same account need to talk; engineer is about to wire it through a public URL.
compatibility_datewas bumped and something started 500-ing.wrangler tailshows the deploy succeeded but the new code isn't running.
The trap this prevents: treating wrangler.toml/wrangler.jsonc as docstring-like config. Several keys are non-inheritable across envs, several have implicit ordering, and the Durable Object migrations array is append-only with strict semantics. Most "it broke in prod" Workers incidents trace to one of these.
Inputs to collect first
| Input | Why | Example |
|---|---|---|
| Account ID | All Workers are account-scoped | dashboard sidebar |
| Worker name | Becomes <name>.<subdomain>.workers.dev and route target |
checkout-api |
| Routes vs Custom Domain | Decide before deploying — they conflict on the same hostname | api.example.com/* (route) or api.example.com (custom domain) |
| Bindings list | KV / R2 / D1 / Queues / DOs / services / AI / Vectorize | [{type: kv, id: ...}, {type: do, class: Counter}] |
| Environments | staging, production, ephemeral PR envs |
dictates env block structure |
compatibility_date |
Behavior pin; not metadata | 2025-05-01, recent but not future |
| Static assets | Yes/no; SPA vs MPA; needs Worker handler? | ./dist, SPA, no |
API token scopes for deploy: see references/recipes/ci-deploy.md for the full per-resource list.
What ships with it
12 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.
- evals/do-class-rename.json 1.7 KB
- evals/env-override-trap.json 1.6 KB
- evals/pages-to-static-assets.json 2.1 KB
- evals/secret-in-vars.json 1.6 KB
- evals/service-binding-vs-fetch.json 2.1 KB
- evals/toml-vs-jsonc.json 992 B
- references/recipes/bindings.md 6.3 KB
- references/recipes/ci-deploy.md 6.0 KB
- references/recipes/durable-objects.md 6.5 KB
- references/recipes/static-assets.md 6.1 KB
- references/recipes/wrangler-config.md 5.9 KB
- scripts/validate_wrangler.py 14 KB runs code
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 · 120 lines · 163 tokens per session scan A 5cf1e1b4ef0f
cloudflare-workers is a skill published in the GitHub repository Goodsmileduck/claude-registry (1 stars, last pushed 3mo ago), licensed MIT. It adds 163 tokens to every session and 2,327 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
stripe-projects
Provision SaaS services + sync creds via Stripe Projects.
multi-tenant-architecture
Designs tenant isolation, hostname routing, custom-domain lifecycle, and plan limits on Cloudflare or Vercel. Use when asked to "isolate tenant data", "support custom domains", "build a white-label platform", or assess PSL registration. For general module structure use codebase-architecture; for SEO content use seo.
netlify-development
Best practices for building and deploying Netlify sites, covering serverless and edge functions, Netlify Blobs storage, the Image CDN, and build configuration. Use when writing Netlify Functions or Edge Functions, configuring netlify.toml or redirects/headers, managing environment variables across deploy contexts…
cloudflare-development
Cloudflare Workers, Pages, KV, D1, R2, and Durable Objects development best practices for edge computing applications.
gcp-development
Google Cloud Platform (GCP) development best practices for Cloud Functions, Cloud Run, Firestore, BigQuery, and Infrastructure as Code.
event-driven-architecture
Kafka, RabbitMQ, SQS/SNS, event sourcing, CQRS, saga patterns, dead letter queues, and idempotency. Use when designing asynchronous systems, implementing message-driven workflows, or building event streaming pipelines.