cloudflare-kv:setup

cloudflare-kv:setup is a command for coding agents from secondsky/claude-skills. It costs 24 tokens per session (1,051 once invoked), scanned A, original, MIT.

An interactive setup command for creating and configuring Cloudflare Workers KV namespaces. KV is a key-value storage service used by applications to save and retrieve data.

In plain words
What is it for?
It is for creating production and preview namespaces, updating wrangler.jsonc, generating TypeScript examples, and testing access.
Why use it?
It handles namespace creation, environment bindings, type definitions, and connection checks in one guided process.

Command

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the cloudflare-kv plugin — 1 skill, 3 commands, 2 agents shipped together

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/secondsky/claude-skills/setup-kv
Clone the repo
git clone --depth 1 https://github.com/secondsky/claude-skills

Or install cloudflare-kv, the plugin that ships this one along with the rest of its 1 skill, 3 commands, 2 agents.

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

agentmods badge for cloudflare-kv:setup

README.md
[![agentmods](https://agentmods.dev/badge/commands/secondsky/claude-skills/setup-kv.svg)](https://agentmods.dev/commands/secondsky/claude-skills/setup-kv)
Your own site
<a href="https://agentmods.dev/commands/secondsky/claude-skills/setup-kv"><img src="https://agentmods.dev/badge/commands/secondsky/claude-skills/setup-kv.svg" alt="Measured on agentmods" height="20"></a>
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,051 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00024 $0.01051
Opus 5 $0.00012 $0.00526
Sonnet 5 $0.00005 $0.00210
Haiku 4.5 $0.00002 $0.00105

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

Security

Grade A, and why

cloudflare-kv:setup 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 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

async fetch(request, env: Env) {
plugins/cloudflare-kv/skills/cloudflare-kv/commands/setup-kv.md · 199 lines

How it starts

The opening of the file, as written. The whole thing — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/cloudflare-kv:setup - Interactive KV Namespace Setup

This command guides through the complete setup process for Cloudflare Workers KV namespaces.

What This Command Does

  1. Creates KV Namespaces

    • Production namespace
    • Preview namespace (for testing)
    • Generates unique IDs for both
  2. Configures wrangler.jsonc

    • Adds KV namespace bindings
    • Sets up preview environment
    • Creates config if needed
  3. Generates TypeScript Types

    • Env interface with KV bindings
    • Type-safe Worker code examples
  4. Tests Connection

    • Validates configuration
    • Performs basic CRUD operations
    • Verifies namespace accessibility

How to Use

Interactive Mode (Recommended)

Run the command and follow prompts:

/cloudflare-kv:setup

The command will:

  1. Ask for namespace name (e.g., "MY_KV" or "USER_DATA")
  2. Create production and preview namespaces
  3. Generate wrangler.jsonc configuration
  4. Provide TypeScript setup examples
  5. Offer to run connection tests

With Namespace Name

Provide namespace name upfront:

/cloudflare-kv:setup MY_NAMESPACE

Implementation

Execute the setup script from the cloudflare-kv skill:

${CLAUDE_PLUGIN_ROOT}/scripts/setup-kv-namespace.sh [namespace-name]

The script will:

  • Check wrangler CLI installation
  • Verify authentication status
  • Create namespaces via wrangler API
  • Extract namespace IDs
  • Generate configuration snippets
  • Optionally create/update wrangler.jsonc

Prerequisites

Before running this command, ensure:

  1. Wrangler CLI Installed

    npm install -g wrangler
    
  2. Authenticated with Cloudflare

    wrangler login
    
  3. Active Cloudflare Account

    • Workers plan enabled
    • API access configured

Example Output

Cloudflare Workers KV - Namespace Setup Wizard
================================================

Creating KV namespaces for: MY_KV_NAMESPACE

Step 1: Creating production namespace...
✓ Production namespace created
   ID: a1b2c3d4e5f6789012345678901234ab

Step 2: Creating preview namespace...
✓ Preview namespace created
   ID: b2c3d4e5f6789012345678901234abc1

✓ Namespaces created successfully!

Step 3: Generating wrangler.jsonc configuration...

Add this to your wrangler.jsonc:

  "kv_namespaces": [
    {
      "binding": "MY_KV_NAMESPACE",
      "id": "a1b2c3d4e5f6789012345678901234ab",
      "preview_id": "b2c3d4e5f6789012345678901234abc1"
    }
  ]

Step 4: TypeScript type definition example...

Add this to your Worker code for TypeScript support:

type Env = {
  MY_KV_NAMESPACE: KVNamespace;
};

✓ Setup complete!

Next steps:
1. Ensure wrangler.jsonc has the KV namespace configuration
2. Use env.MY_KV_NAMESPACE in your Worker code
3. Test with: wrangler dev

Read the full file on GitHub · 199 lines

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 · 199 lines · 24 tokens per session scan A b63c55d29d94

Subscribe to this mod's changes

cloudflare-kv:setup is a command published in the GitHub repository secondsky/claude-skills (214 stars, last pushed 2d ago), licensed MIT. It adds 24 tokens to every session and 1,051 once invoked, about $0.0001 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-09-03.