jezweb/claude-skills is a collection of skills, commands, plugins, settings, instructions, and hooks that guide the Claude Code CLI through development tasks and produce outputs such as project scaffolds, assets, documents, or deployed services. It is for developers using Claude Code with technologies and services including Cloudflare, React, Tailwind, Shopify, and WordPress. The catalogue entries are the project's own Claude Code workflow components.
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.
git clone --depth 1 https://github.com/jezweb/claude-skillsWrote 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/commands/jezweb/claude-skills/cloudflare-api)<a href="https://agentmods.dev/commands/jezweb/claude-skills/cloudflare-api"><img src="https://agentmods.dev/badge/commands/jezweb/claude-skills/cloudflare-api/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/commands/jezweb/claude-skills/cloudflare-api"><img src="https://agentmods.dev/badge/commands/jezweb/claude-skills/cloudflare-api.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.00017 | $0.00196 |
| Opus 5.5 | $0.00007 | $0.00078 |
| Sonnet 5.5 | $0.00003 | $0.00039 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade A, and why
cloudflare-api 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 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.
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.
What it actually says
Load the cloudflare-api skill.
Parse $ARGUMENTS for operation type and target domain:
dns example.com— bulk DNS operationshostname example.com— custom hostname managementemail example.com— email routing rulescache example.com— cache purgewaf example.com— WAF/firewall rulesredirect example.com— redirect rulessettings— zone settings (fleet-wide)routes example.com— Worker route managementanalytics example.com— GraphQL analytics query
If no type specified, ask what they need. If no domain, use the current project's domain from wrangler.jsonc.
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 · 20 lines · 17 tokens per session scan A d24adcf8355f
cloudflare-api is a command published in the GitHub repository jezweb/claude-skills (1,065 stars, last pushed 7d ago), licensed MIT. It adds 17 tokens to every session and 196 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
start
You are turning a fresh copy of the Cloudflare Workers + React template into the user's own project and getting it live. Users range from first-time builders to experienced developers.
add-binding
I'll add a Cloudflare binding to this Worker: update wrangler.jsonc, regenerate types, and show a minimal usage example. Bindings are reached through env and are typed once pnpm cf-typegen has run.
nyann:apply
Apply an Infrastructure-as-Code change — the highest-stakes mutator in nyann; it can change real cloud infrastructure. Re-runs the plan, shows it, confirms, then applies. Unmistakably opt-in: apply is never the default and destructive applies require a second explicit confirm. For IaC apply intent only (not "apply a…
deploy-verify
Run the server-side verification of a deployment and report pass or fail per check. Use when a deploy finished, after a cutover, or before closing a release.
plan-platform-migration
Plan a move to a new platform or provider, with parallel running and a reversible cutover.
saas
One-line SaaS — from a description, scaffold a complete CF-native multi-tenant SaaS (Hono + D1 + Drizzle + Better Auth + Stripe + shadcn) deployed to a real URL.