debugging-durable-objects

A set of instructions for diagnosing Savecraft’s Durable Objects, which are stateful server components named SourceHub and UserHub. It uses an authenticated admin inspection API to examine sources, events, and stored state.

In plain words
What is it for?
Use it when sources are offline, events do not reach the interface, state looks wrong, daemon connections fail, or sources become stale.
Why use it?
It helps locate whether a problem comes from source connectivity, missing events, stored object state, daemon connections, or internal errors.

Skill for Claude CodeCodex

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 skills/joshsymonds/savecraft.gg/debugging-durable-objects
Any agent
npx skills add joshsymonds/savecraft.gg --skill debugging-durable-objects
Clone the repo
git clone --depth 1 https://github.com/joshsymonds/savecraft.gg

Made for: Claude Code, Codex.

Per session 95 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,517 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.00095 $0.01517
Opus 5 $0.00048 $0.00758
Sonnet 5 $0.00019 $0.00303
Haiku 4.5 $0.00010 $0.00152

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

Security

Grade A, and why

debugging-durable-objects 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 2d 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.

.claude/skills/debugging-durable-objects/SKILL.md · 129 lines

How it starts

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

Debugging Durable Objects

Use the admin introspection API to diagnose SourceHub and UserHub issues. Full architecture details in docs/worker.md under "Debug Introspection".

Auth

All admin endpoints require Authorization: Bearer $ADMIN_API_KEY.

Environment Where the key lives
Production wrangler secret (set via wrangler secret put ADMIN_API_KEY --env production)
Staging wrangler secret (set via wrangler secret put ADMIN_API_KEY --env staging)
Local dev worker/.dev.varsADMIN_API_KEY=...
Tests worker/vitest.config.ts miniflare bindings

Base URLs: production https://api.savecraft.gg, staging https://staging-api.savecraft.gg, local http://localhost:8787.

Endpoints

Discovery (D1)

Endpoint Returns
GET /admin/sources All sources: source_uuid, user_uuid, hostname, source_kind, timestamps. Capped at 200.
GET /admin/source/:uuid/events?limit=N D1 source_events rows (default 50, max 500). Includes event_type, event_data, created_at.

SourceHub Debug (per-source DO)

Endpoint Returns
GET /admin/source/:uuid/debug/state sourceState (sources array with online/lastSeen/games), sourceUuid, userUuid, sourceMeta, alarm timestamp
GET /admin/source/:uuid/debug/connections daemonCount, connections array with tags per socket
GET /admin/source/:uuid/debug/log?level=X&limit=N Ring buffer entries (newest first). Levels: debug, info, warn, error. Limit capped at 200.
GET /admin/source/:uuid/debug/storage All DO transactional storage key names

UserHub Debug (per-user DO)

Endpoint Returns
GET /admin/user/:uuid/debug/state mergedState (all sources merged), userUuid
GET /admin/user/:uuid/debug/connections uiCount (active UI WebSocket count)
GET /admin/user/:uuid/debug/log?level=X&limit=N Ring buffer entries. Same filters as SourceHub.
GET /admin/user/:uuid/debug/storage All DO storage key names

Read the full file on GitHub · 129 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. 2d ago First seen · 129 lines · 95 tokens per session scan A d1f6ecfe9b2f

Subscribe to this mod's changes

debugging-durable-objects is a skill published in the GitHub repository joshsymonds/savecraft.gg (12 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 95 tokens to every session and 1,517 once invoked, about $0.0005 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens