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 agentmods add skills/ericrisco/rsc-harness/cloudflarenpx skills add ericrisco/rsc-harness --skill cloudflaregit clone --depth 1 https://github.com/ericrisco/rsc-harnessWrote 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/ericrisco/rsc-harness/cloudflare)<a href="https://agentmods.dev/skills/ericrisco/rsc-harness/cloudflare"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/cloudflare.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 | $0.00086 | $0.02641 |
| Opus 5 | $0.00043 | $0.01321 |
| Sonnet 5 | $0.00017 | $0.00528 |
| Haiku 4.5 | $0.00009 | $0.00264 |
Grade A, and why
cloudflare 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 5d 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.
"binding": "ASSETS", // env.ASSETS.fetch(request) How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloudflare Workers & edge primitives
The model in one paragraph
A Worker is a fetch handler that runs at the edge. Everything else — R2, D1, KV, Queues, static assets, Durable Objects — is a binding declared in wrangler.jsonc and reached through env. If a resource is not bound, it is not reachable from your code. There is no connection string and no import of the bucket; you wire it in config, type it on Env, and call env.BINDING. Hold this picture and most "how do I access X" questions answer themselves: declare the binding, redeploy, use env.
Quick start
npm create cloudflare@latest (the C3 scaffolder) bootstraps a Worker or a full framework. Use it — it pins a correct compatibility_date and generates types.
npm create cloudflare@latest my-app # plain Worker
npm create cloudflare@latest my-app -- --framework=react # Vite + React SPA, GA plugin
cd my-app
npx wrangler dev # local edge emulation at http://localhost:8787
npx wrangler deploy # ships Worker + bound assets in one operation
Wrangler is v4 (an incremental release over the v3 rewrite — same config model, updated deps). Pin it: npx wrangler@4.
wrangler.jsonc anatomy
Config may be wrangler.toml, wrangler.json, or wrangler.jsonc. Prefer jsonc so you can comment bindings. Minimum keys: name, main, compatibility_date.
{
"name": "my-app",
"main": "src/index.ts",
// Set to TODAY's date when you start. Why: it pins runtime + flag behavior;
// bumping it later opts into new defaults (e.g. nodejs_compat auto-enables at 2025-10-01+).
"compatibility_date": "2026-06-02",
"compatibility_flags": ["nodejs_compat"],
// Static Assets — the default way to host a SPA / full-stack app.
"assets": {
"directory": "./dist",
"binding": "ASSETS", // env.ASSETS.fetch(request)
"not_found_handling": "single-page-application"
},
// Non-secret config only. Secrets go via `wrangler secret put`, never here.
"vars": { "API_BASE": "https://api.example.com" },
"r2_buckets": [{ "binding": "BUCKET", "bucket_name": "uploads" }],
"d1_databases": [{ "binding": "DB", "database_name": "app", "database_id": "<id>" }],
"kv_namespaces":[{ "binding": "CACHE", "id": "<namespace-id>" }],
"queues": {
"producers": [{ "binding": "JOBS", "queue": "thumbnails" }],
"consumers": [{ "queue": "thumbnails", "max_batch_size": 10, "max_retries": 3,
"dead_letter_queue": "thumbnails-dlq" }]
}
}
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.
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.
- 5d ago First seen · 187 lines · 86 tokens per session scan A 935c9b50eeef
cloudflare is a skill published in the GitHub repository ericrisco/rsc-harness (60 stars, last pushed 2d ago), licensed MIT. It adds 86 tokens to every session and 2,641 once invoked, about $0.0004 per session on Opus 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-30.
Other skills, from other repositories
hono-cloudflare
Hono on Cloudflare Workers - bindings, KV, D1, R2, Durable Objects, and edge deployment patterns.
cloudflare-worker-dev
Cloudflare Workers, KV, Durable Objects, and edge computing development. Use for serverless APIs, caching, rate limiting, real-time features. Activate on "Workers", "KV", "Durable Objects", "wrangler", "edge function", "Cloudflare". NOT for Cloudflare Pages configuration (use deployment docs), DNS management, or…
cloudflare-workers-debugging
Use when wrangler deploys silently fail or produce wrong artifacts, secrets upload as empty strings, custom domain DNS is not resolving, route assignment broke after rename, observability/tail logs are needed, D1/KV/R2 bindings are missing, OAuth scope errors block a command, cookies on a redirect are not attaching…
Cloudflare Workers & Edge AI Development
Build ultra-low-latency edge computing applications with Cloudflare Workers, Workers AI for LLM inference, V8 isolates, Durable Objects, and serverless patterns deployed across 330+ data centers worldwide.
cloudflare-workers-local-dev
Patterns, pitfalls, and workflows for local Cloudflare Workers development with D1, static assets, multi-source integration, and the m-log refactoring architecture.
edge-computing-patterns
Deploy to edge runtimes (Cloudflare Workers, Vercel Edge, Deno Deploy) for globally distributed, low-latency applications. Master edge middleware, streaming, and runtime constraints for 2025+ edge computing.