Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add secondsky/claude-skills/plugin install cloudflare-kvWrote 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/secondsky/claude-skills/test-kv)<a href="https://agentmods.dev/commands/secondsky/claude-skills/test-kv"><img src="https://agentmods.dev/badge/commands/secondsky/claude-skills/test-kv/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/secondsky/claude-skills/test-kv"><img src="https://agentmods.dev/badge/commands/secondsky/claude-skills/test-kv.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.00023 | $0.01231 |
| Opus 5.5 | $0.00009 | $0.00492 |
| Sonnet 5.5 | $0.00005 | $0.00246 |
| Haiku 4.5 | $0.00002 | $0.00123 |
Grade A, and why
cloudflare-kv:test 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.
How it starts
The opening of the file, as written. The whole thing — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/cloudflare-kv:test - Test KV Namespace Connection
This command validates KV namespace configuration and tests basic operations to ensure everything is working correctly.
What This Command Does
-
Validates Configuration
- Checks wrangler.jsonc for KV bindings
- Verifies namespace ID format
- Confirms binding name correctness
-
Tests CRUD Operations
- PUT: Creates test key-value pair
- GET: Retrieves and validates value
- DELETE: Removes test key
- Verifies cleanup after deletion
-
Reports Diagnostics
- Operation success/failure status
- Error messages with troubleshooting hints
- Configuration recommendations
How to Use
Basic Usage
Test a specific namespace binding:
/cloudflare-kv:test MY_NAMESPACE
Replace MY_NAMESPACE with your actual binding name from wrangler.jsonc.
Interactive Mode
If no namespace provided, the command will:
- List available namespaces from wrangler.jsonc
- Ask which one to test
- Run comprehensive tests
/cloudflare-kv:test
Implementation
Execute the test script from the cloudflare-kv skill:
${CLAUDE_PLUGIN_ROOT}/scripts/test-kv-connection.sh <NAMESPACE_BINDING>
The script performs:
- Configuration validation
- Test key generation (timestamped, unique)
- PUT operation test
- GET operation and value verification
- DELETE operation test
- Cleanup verification
Prerequisites
-
Wrangler CLI Installed
npm install -g wrangler -
Authenticated
wrangler whoami # Verify authentication -
Namespace Configured
- wrangler.jsonc must have kv_namespaces section
- Namespace ID must be valid
Example Output
Successful Test
Cloudflare Workers KV - Connection Tester
==========================================
Testing namespace: MY_KV_NAMESPACE
Step 1: Checking namespace configuration...
✓ Namespace binding found in wrangler.jsonc
✓ Namespace ID: a1b2c3d4e5f6789012345678901234ab
Step 2: Testing KV operations...
Test key: __test_connection_1735300800
Testing PUT operation... ✓ Success
Testing GET operation... ✓ Success (value matches)
Testing DELETE operation... ✓ Success
Verifying deletion... ✓ Success (key removed)
Summary:
========
✓ All tests passed!
Your KV namespace 'MY_KV_NAMESPACE' is working correctly.
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 · 246 lines · 23 tokens per session scan A 4a64dd75c9f4
cloudflare-kv:test is a command published in the GitHub repository secondsky/claude-skills (231 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 1,231 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-09-03.
Other commands, from other repositories
correlate
Find related failures through pattern matching.
diff
Compare two command outputs with intelligent diff.
open
Open/retrieve an offloaded output by ID or shortcut.
search
Search through offloaded outputs with hard caps.
stats
Show FewWord session statistics with rich output and token savings.
config
Show effective FewWord configuration with sources.