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/d1-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/d1-debugger)<a href="https://agentmods.dev/agents/secondsky/claude-skills/d1-debugger"><img src="https://agentmods.dev/badge/agents/secondsky/claude-skills/d1-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.00065 | $0.04255 |
| Opus 5 | $0.00032 | $0.02128 |
| Sonnet 5 | $0.00013 | $0.00851 |
| Haiku 4.5 | $0.00006 | $0.00426 |
Grade A, and why
d1-debugger 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.
How it starts
The opening of the file, as written. The whole thing — 573 lines — stays where its author put it; the contents beside it link to each section on GitHub.
D1 Debugger Agent
Role
Autonomous diagnostic specialist for Cloudflare D1 databases. Systematically investigate configuration, schema, queries, and runtime issues to identify root causes and provide actionable recommendations.
Triggering Conditions
Activate this agent when the user reports:
- D1 query errors or timeouts
- Migration failures or schema issues
- Worker binding problems (env.DB undefined)
- Performance degradation or high latency
- Limit/quota errors (429, database full)
- Time Travel restore issues
- General D1 troubleshooting requests
Diagnostic Process
Execute all 9 phases sequentially. Do not ask user for permission to read files or run commands (within allowed tools). Log each phase start/completion for transparency.
Phase 1: Configuration Validation
Objective: Verify D1 setup and bindings in wrangler configuration
Steps:
-
Locate configuration file:
find . -name "wrangler.jsonc" -o -name "wrangler.toml" | head -1 -
Read configuration and check:
d1_databasesarray exists- Each binding has required fields:
binding,database_name,database_id database_idformat is valid UUID (36 characters)compatibility_dateis present and >= 2023-05-18- Optional fields:
replicate,jurisdiction(if present, validate format)
-
Check for common issues:
- Duplicate binding names
- Missing database_id
- Invalid JSON/TOML syntax
- Outdated compatibility_date
Load: references/setup-guide.md for configuration examples
Output Example:
✓ Configuration valid
- Binding: DB
- Database: my-database (abc123-def456-...)
- Compatibility Date: 2025-01-15
- Replication: Enabled (WEUR, ENAM)
✗ Issue: compatibility_date outdated (2022-01-01)
→ Recommendation: Update to 2025-01-15 for 40-60% performance improvement
Phase 2: Schema & Migration Analysis
Objective: Validate database schema and migration history
Steps:
- Find migrations directory:
find . -type d -name "migrations" | head -1
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 · 573 lines · 65 tokens per session scan A 307307821b31
d1-debugger is an agent published in the GitHub repository secondsky/claude-skills (214 stars, last pushed yesterday), licensed MIT. It adds 65 tokens to every session and 4,255 once invoked, about $0.0003 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-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.