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 skills add resonatehq/resonate-skills --skill resonate-migrate-from-dbosgit clone --depth 1 https://github.com/resonatehq/resonate-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/skills/resonatehq/resonate-skills/resonate-migrate-from-dbos)<a href="https://agentmods.dev/skills/resonatehq/resonate-skills/resonate-migrate-from-dbos"><img src="https://agentmods.dev/badge/skills/resonatehq/resonate-skills/resonate-migrate-from-dbos/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/skills/resonatehq/resonate-skills/resonate-migrate-from-dbos"><img src="https://agentmods.dev/badge/skills/resonatehq/resonate-skills/resonate-migrate-from-dbos.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.00119 | $0.04044 |
| Opus 5 | $0.00060 | $0.02022 |
| Sonnet 5 | $0.00024 | $0.00809 |
| Haiku 4.5 | $0.00012 | $0.00404 |
Grade A, and why
resonate-migrate-from-dbos 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 12d 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrate from DBOS to Resonate
A pattern-by-pattern playbook for porting a DBOS application to Resonate. Identify which DBOS construct each piece of the source uses, apply the matching transform, and reach for the linked per-SDK skill for idiomatic target code.
Ground rules
- Never invent DBOS code. Quote it from the user's source or a named
dbos-inc/dbos-demo-apps/dbos-transact-*file. If you can't find it, say so. - DBOS has SDKs for TypeScript, Python, Go, and Java — but no Rust SDK. Don't emit DBOS Rust. When migrating to Resonate Rust, map from the DBOS Python or TypeScript idiom.
- Resonate has no
@DBOS.workflow/@DBOS.stepsplit. A step is just a function made durable byctx.run. Don't invent decorators or a step type. - A DBOS workflow must be deterministic — side effects live in steps. The same
discipline carries to Resonate: do side-effecting work inside
ctx.runso it is checkpointed, not re-executed on replay. - State coverage honestly. A missing example ≠ impossible; it means no worked reference exists yet.
- Verify APIs against the pinned version before emitting — both the DBOS and Resonate SDK surfaces drift between versions.
Pinned SDK versions (latest released at time of writing)
| SDK | Resonate (target) | DBOS (source) |
|---|---|---|
| TypeScript | @resonatehq/sdk v0.11.4 (npm) |
@dbos-inc/dbos-sdk v4.19.8 (npm) |
| Python | resonate-sdk v0.7.4 (PyPI) |
dbos v2.23.0 (PyPI) |
| Rust | resonate-sdk v0.6.0 (crates.io) |
— (no DBOS Rust SDK) |
| Go | 0.1.0 (tag has no v prefix — go get github.com/resonatehq/[email protected]) |
dbos-transact-golang v0.17.0 |
Core mappings (apply everywhere)
| DBOS | Resonate |
|---|---|
@DBOS.workflow() / DBOS.registerWorkflow(fn) / dbos.RegisterWorkflow(ctx, fn) |
a registered function (@resonate.register, resonate.register("name", fn), #[resonate::function], resonate.Register(r, "name", fn)) |
@DBOS.step() / DBOS.runStep(fn) / dbos.RunAsStep(ctx, fn) |
a plain function invoked via ctx.run(fn, args) |
DBOS.start_workflow(fn, ...) / DBOS.startWorkflow(fn)(...) / dbos.RunWorkflow(ctx, fn, args) (child workflow) |
ctx.rpc("name", args) or ctx.run(fn, args) — invoke by registered name; recursion is trivial |
durable queue: DBOS.register_queue + DBOS.enqueue_workflow(...) then handle.get_result() (fan-out) |
start each non-blocking (ctx.beginRun / ctx.rfi / .spawn() / ctx.RPC), then await each |
DBOS.recv(topic, timeout) (block for a message) |
one latent durable promise: p = ctx.promise() then await p |
DBOS.send(destId, msg, topic) (deliver from outside) |
resonate.promises.resolve(id, value) (HTTP-addressable from anywhere) |
DBOS.set_event(key, value) / DBOS.get_event(wfId, key) (publish/read status) |
the promise's own resolved value is the status; read it by id |
DBOS.sleep(...) |
ctx.sleep(duration) |
@DBOS.scheduled(cron) / DBOS.create_schedule(...) / dbos.WithSchedule(cron) |
resonate.schedule(id, cron, fn) (ts/rust) or resonate.schedules.create(...) (py) |
| try/except + explicit undo step (no saga DSL) | inline ctx.run(undo, …) in the error branch, guarded by what completed |
systemDatabaseUrl Postgres (or Python SQLite default) |
nothing — the Worker runs in-memory until you connect a Resonate Server |
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.
- 12d ago First seen · 220 lines · 119 tokens per session scan A b416659d7807
resonate-migrate-from-dbos is a skill published in the GitHub repository resonatehq/resonate-skills (6 stars, last pushed 21d ago), licensed Apache-2.0. It adds 119 tokens to every session and 4,044 once invoked, about $0.0006 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-31.
Other skills, from other repositories
workflow
Creates durable, resumable workflows using Vercel's Workflow SDK. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of "workflow", "durable functions", "resumable", "workflow sdk", "queue"…
migrating-workflow-v4-to-v5
Upgrades an app from Workflow SDK 4.x to 5.0. Use when bumping the workflow / @workflow/ dependencies to v5, or when hitting removed v4 APIs — runStep, stepEntrypoint, workflow/internal/private, @workflow/core/private, writeToStream / closeStream / readFromStream on a World, world.steps.get without a runId…
migrating-to-workflow-sdk
Migrates Temporal, Inngest, Trigger.dev, and AWS Step Functions workflows to the Workflow SDK. Use when porting Activities, Workers, Signals, step.run(), step.waitForEvent(), Trigger.dev tasks / wait.forToken / triggerAndWait, ASL JSON state machines, Task/Choice/Wait/Parallel states, task tokens, or child workflows.
deepep-to-cam-converter
A code migration skill for replacing DeepEP communication operations with CAM operations when moving mixture-of-experts code from CUDA/NCCL to Ascend NPUs.
e2a-doctor
Use when an existing e2a MCP connection, inbox, custom domain, protection policy, webhook, or message delivery is failing or unclear. Diagnoses read-only through MCP first, ranks evidence-backed causes, and offers individually confirmed repairs; uses the CLI doctor only when CLI or self-hosted diagnostics are…
e2a-integrate
Use when adding e2a email capabilities to an application or codebase: outbound sending, inbound signed webhooks, REST polling, or SDK integration. Inspects the existing language and framework, uses official TypeScript/Python SDKs or idiomatic REST/OpenAPI, adds tests, and keeps credentials server-side.