cloudflare-api

A command for calling Cloudflare's web service API for account and domain operations. It covers tasks such as DNS, cache, firewall, redirects, routes, email rules, settings, and analytics.

In plain words
What is it for?
Use it to manage DNS records, custom hostnames, email routing, cache purges, firewall rules, redirects, Worker routes, settings, or analytics for a domain.
Why use it?
It handles bulk or operational Cloudflare work that the usual Wrangler command-line tool may not cover.

Command

Install

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.

agentmods
npx agentmods add commands/jezweb/claude-skills/cloudflare-api
Clone the repo
git clone --depth 1 https://github.com/jezweb/claude-skills
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 196 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00017 $0.00196
Opus 5 $0.00009 $0.00098
Sonnet 5 $0.00003 $0.00039
Haiku 4.5 $0.00002 $0.00020

Measured yesterday against content hash d24adcf8355f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

plugins/cloudflare/commands/cloudflare-api.md · 20 lines

What it actually says

Load the cloudflare-api skill.

Parse $ARGUMENTS for operation type and target domain:

  • dns example.com — bulk DNS operations
  • hostname example.com — custom hostname management
  • email example.com — email routing rules
  • cache example.com — cache purge
  • waf example.com — WAF/firewall rules
  • redirect example.com — redirect rules
  • settings — zone settings (fleet-wide)
  • routes example.com — Worker route management
  • analytics 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.

Changes

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.

  1. yesterday First seen · 20 lines · 17 tokens per session scan A d24adcf8355f

Subscribe to this mod's changes

cloudflare-api is a command published in the GitHub repository jezweb/claude-skills (982 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 196 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.