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/nevaberry/nevaberry-plugins/cloudflare-workers-knowledge-patchnpx skills add Nevaberry/nevaberry-plugins --skill cloudflare-workers-knowledge-patchgit clone --depth 1 https://github.com/Nevaberry/nevaberry-pluginsWhat 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.00011 | $0.01961 |
| Opus 5 | $0.00005 | $0.00981 |
| Sonnet 5 | $0.00002 | $0.00392 |
| Haiku 4.5 | $0.00001 | $0.00196 |
Grade A, and why
cloudflare-workers-knowledge-patch 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 3d 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloudflare Workers Knowledge Patch
Use this skill when implementing, migrating, testing, or deploying Cloudflare Workers. Start with the compatibility date and Wrangler configuration, then open only the reference files relevant to the task.
Reference index
| Reference | Topics |
|---|---|
| runtime-compatibility.md | Compatibility gates, Fetch and Cache behavior, JavaScript and stream APIs, Access, tracing, Dynamic Workers |
| nodejs-compatibility.md | nodejs_compat, process and environment behavior, native APIs, stubs, timers, runtime types |
| rpc-and-websockets.md | Workers RPC capabilities and ownership, pipelining, cross-language calls, WebSocket behavior |
| static-assets-and-pages-migration.md | Static Assets routing and deployment, Pages migration, preview and domain caveats |
| vite-development-and-testing.md | Vite plugin configuration, auxiliary Workers, production-build integration tests, local traces |
| wrangler-and-deployment.md | Wrangler v4 migration, local versus remote resources, authentication, types, startup inspection, Builds |
Triage compatibility-date changes first
Before changing code, read compatibility_date and compatibility_flags from
the active Wrangler configuration. Many runtime differences below are date
gated and have explicit rollback flags.
For dates from 2026-08-04, Node.js compatibility is on by default. Opting out
requires both flags:
{
"compatibility_date": "2026-08-04",
"compatibility_flags": ["no_nodejs_compat", "no_nodejs_compat_v2"]
}
Earlier dates do not change. Positive Node.js compatibility flags on a new date are redundant and local tooling may ignore them.
When upgrading an existing Worker, specifically regression-test:
process.envpopulation at2025-04-01withnodejs_compat.- Static Asset navigation fallback ordering at
2025-04-01. - cross-origin
Authorizationstripping at2025-09-01. - optional runtime properties becoming present with
undefinedat2025-12-03. require()default-export interop at2026-01-22.- iterable request and response bodies at
2026-02-19. - WebSocket close, binary, and half-open behavior in March 2026.
- Node-compatible timer handles at
2026-02-10.
What ships with it
7 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.
- 3d ago First seen · 215 lines · 11 tokens per session scan A 216d7cf89d69
cloudflare-workers-knowledge-patch is a skill published in the GitHub repository Nevaberry/nevaberry-plugins (24 stars, last pushed 6d ago), licensed MIT. It adds 11 tokens to every session and 1,961 once invoked, about $0.0001 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-30.
Other skills, from other repositories
api-workers
Cloudflare Workers deployment using createWorkerHandler from @cyanheads/mcp-ts-core/worker. Covers the full handler signature, binding types, CloudflareBindings extensibility, runtime compatibility guards, and wrangler.toml requirements.
infrastructure-planning
Plan and document the required software, infrastructure, and logistics for a Paperclip company — domains, GitHub, Docker Hub, Kubernetes, Slack, Google Workspace, Stripe, shipping providers, and CI/CD pipelines. Use when setting up infrastructure for a new company or auditing what an existing company needs.
kubernetes
Kubernetes and GKE operations: kubectl, manifests, deployments, services, workload identity, autopilot, config connector, private clusters, and troubleshooting.
istio
Istio service mesh: traffic management, gateways, virtual services, destination rules, mTLS, authorization policies, EnvoyFilters, and observability.
terraform
Terraform infrastructure-as-code for provisioning cloud and Kubernetes resources: modules, state and backends, providers, and plan/apply workflows.
auth
Authentication/authorization infra with Keycloak and OAuth2-proxy. Use for identity providers, SSO, OIDC/SAML, realm/client config, user federation, and OAuth2-proxy sidecar or ingress auth on Kubernetes.