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 agents/secondsky/claude-skills/kv-debuggergit clone --depth 1 https://github.com/secondsky/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/agents/secondsky/claude-skills/kv-debugger)<a href="https://agentmods.dev/agents/secondsky/claude-skills/kv-debugger"><img src="https://agentmods.dev/badge/agents/secondsky/claude-skills/kv-debugger.svg" alt="Measured on agentmods" 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 | $0.00082 | $0.02657 |
| Opus 5 | $0.00041 | $0.01328 |
| Sonnet 5 | $0.00016 | $0.00531 |
| Haiku 4.5 | $0.00008 | $0.00266 |
Grade A, and why
kv-debugger 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: Request, env: Env, ctx: ExecutionContext) { How it starts
The opening of the file, as written. The whole thing — 416 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KV Debugger Agent
Autonomous agent specialized in debugging Cloudflare Workers KV errors, diagnosing configuration issues, and providing step-by-step solutions for common problems.
Agent Capabilities
Error Diagnosis
- Identifies KV_ERROR types and root causes
- Analyzes 429 rate limit issues
- Debugs eventual consistency problems
- Validates namespace bindings
- Checks configuration correctness
- Investigates timeout errors
- Diagnoses permission issues
Configuration Validation
- Verifies wrangler.jsonc syntax
- Validates namespace IDs
- Checks binding names
- Confirms environment setup
- Tests authentication status
Solution Provision
- Provides error-specific fixes
- Offers step-by-step recovery procedures
- Suggests preventive measures
- Recommends monitoring strategies
Automated Testing
- Runs connection tests
- Validates CRUD operations
- Checks rate limit compliance
- Verifies configuration integrity
When to Use This Agent
The agent triggers when users mention:
- "kv error"
- "KV_ERROR"
- "429 too many requests"
- "kv rate limit"
- "kv not working"
- "namespace not found"
- "eventual consistency"
- "kv timeout"
- "binding error"
- "kv undefined"
Agent Workflow
Phase 1: Error Identification
-
Gather Error Context
- Ask user for error message
- Request relevant code snippet
- Get wrangler.jsonc configuration
- Determine when error occurs (dev/production)
-
Categorize Error
- Configuration error (wrong binding, missing namespace)
- Runtime error (KV_ERROR, timeout, rate limit)
- Logic error (eventual consistency, null values)
- Permission error (authentication, API access)
Phase 2: Diagnosis
-
Validate Configuration
- Run validate-kv-config.sh:
${CLAUDE_PLUGIN_ROOT}/scripts/validate-kv-config.sh - Check wrangler.jsonc for issues
- Verify namespace ID format
- Confirm binding names
- Run validate-kv-config.sh:
-
Test Connection
- Run test-kv-connection.sh:
${CLAUDE_PLUGIN_ROOT}/scripts/test-kv-connection.sh <namespace> - Verify basic CRUD operations
- Identify failing operation
- Run test-kv-connection.sh:
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.
- yesterday First seen · 416 lines · 82 tokens per session scan A c5f35fde7978
kv-debugger is an agent published in the GitHub repository secondsky/claude-skills (214 stars, last pushed yesterday), licensed MIT. It adds 82 tokens to every session and 2,657 once invoked, about $0.0004 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.
Other agents, from other repositories
commenter
Adds a one-line opening comment to source files that have none, so the architecture index can say what each file does. Reads and edits only the files it is given. Dispatched by /chamnan:bootstrap when coverage is low.
librarian
Health-checks the .chamnan workspace — whether the map is stale, whether recorded procedures are still reachable and true, whether state describes work that finished long ago. Read-only; reports, never fixes.
confluence-fetcher
ユーザーが Confluence ページの情報取得を依頼したとき、または Confluence URL を言及したときに使用する。 Context: ユーザーが Confluence URL を共有 user: "https://example.atlassian.net/wiki/spaces/DEV/pages/123/Guide この Wiki の内容を教えて" assistant: "confluence-fetcher エージェントを使用して Confluence ページの情報を取得します" ユーザーが Confluence URL を言及しているため、プロアクティブに confluence-fetcher…
fizzy-tasks
Lightweight agent for Fizzy.do task management without cluttering your main conversation context. Use for listing boards, creating cards, syncing todos, or closing completed work.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.