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 skills/nevaberry/nevaberry-plugins/cloudflare-durable-objects-knowledge-patchnpx skills add Nevaberry/nevaberry-plugins --skill cloudflare-durable-objects-knowledge-patchgit clone --depth 1 https://github.com/Nevaberry/nevaberry-pluginsWhat 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.00015 | $0.01593 |
| Opus 5 | $0.00008 | $0.00796 |
| Sonnet 5 | $0.00003 | $0.00319 |
| Haiku 4.5 | $0.00002 | $0.00159 |
Grade A, and why
cloudflare-durable-objects-knowledge-patch 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.
How it starts
The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloudflare Durable Objects
Use this skill when designing, configuring, deploying, migrating, or testing Cloudflare Durable Objects. Check the project configuration and compatibility date first, then use the topic reference that matches the task.
Reference index
| Reference | Topics |
|---|---|
| deployment-lifecycle.md | SQLite namespace creation, declarative exports, tombstones, renames, transfers, environments, and rollout compatibility |
| storage-and-sql.md | SQL cursors and transactions, SQLite extensions, PITR, synchronous KV, and loopback exports |
| identity-and-placement.md | Object names, jurisdictions, ID spaces, and placement hints |
| concurrency-eviction-and-alarms.md | Gates, atomic writes, hibernation eligibility, eviction, uniqueness, schema migration, shutdown, alarms, and local persistence |
| websocket-hibernation.md | Hibernation handlers, attachments, tags, auto-responses, event timeouts, and closing sockets |
| testing.md | Vitest configuration, binding types, HTTP integration, storage isolation, alarm execution, and eviction helpers |
Breaking and lifecycle decisions
Create new namespaces with SQLite storage
Use new_sqlite_classes in legacy migrations, or storage: "sqlite" in the
declarative exports map. SQLite-backed objects are the recommended default
for new classes and are the only backend with SQL and point-in-time recovery.
Do not assume an existing KV-backed namespace can be converted to SQLite.
Accounts without an existing KV-backed namespace cannot create their first one
with new_classes.
[[migrations]]
tag = "v1"
new_sqlite_classes = ["Room"]
Choose exactly one class-lifecycle system
Use either the ordered migrations array or Wrangler's current-state exports
map in one Worker, never both. Existing Workers can retain migrations. Moving
from migrations to exports preserves namespace data but is one-way, and the
declared storage backend cannot later be changed in place.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 177 lines · 15 tokens per session scan A 9a1657aa4407
cloudflare-durable-objects-knowledge-patch is a skill published in the GitHub repository Nevaberry/nevaberry-plugins (24 stars, last pushed 5d ago), licensed MIT. It adds 15 tokens to every session and 1,593 once invoked, about $0.0001 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.
Other skills, from other repositories
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.enrich, ctx.content), and when to use each.
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…
api-testing
Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.
field-test
Exercise tools, resources, and prompts against a live HTTP server via MCP JSON-RPC over curl. Starts the server, surfaces the catalog, runs real and adversarial inputs, and produces a tight report with concrete findings and numbered follow-up options. Use after adding or modifying definitions, or when the user asks to…
api-config
Reference for core and server configuration in @cyanheads/mcp-ts-core. Covers env var tables with defaults, priority order, server-specific Zod schema pattern, and Workers lazy-parsing requirement.