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 durable-executiongit 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/durable-execution)<a href="https://agentmods.dev/skills/resonatehq/resonate-skills/durable-execution"><img src="https://agentmods.dev/badge/skills/resonatehq/resonate-skills/durable-execution/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/durable-execution"><img src="https://agentmods.dev/badge/skills/resonatehq/resonate-skills/durable-execution.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.00097 | $0.04792 |
| Opus 5 | $0.00048 | $0.02396 |
| Sonnet 5 | $0.00019 | $0.00958 |
| Haiku 4.5 | $0.00010 | $0.00479 |
Grade A, and why
durable-execution 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 11d 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 — 409 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Durable Execution
Your code will crash. Durable execution means: when it restarts, it picks up where it left off — not from the beginning.
Traditional: start → step1 → step2 → crash → lost
Queue-based: start → step1 → step2 → crash → retry from top → duplicates
Durable: start → step1 → step2 → crash → replay to step2 → continue from step3
Everything else — frameworks, protocols, infrastructure — is implementation detail.
Do You Need This?
Score 1–5 on each dimension:
| Dimension | 1 (low) | 5 (high) |
|---|---|---|
| Failure cost | Retry is inexpensive, no side effects | Retry causes duplicates, data loss, or revenue loss |
| Duration | Milliseconds, single request | Hours/days/weeks, spans process lifetimes |
| Coordination | Single service, single step | Multiple services, human gates, external callbacks |
| State complexity | Stateless or simple key-value | Branching workflows, conditional logic, fan-out/fan-in |
| Total | Recommendation |
|---|---|
| 4–8 | Use a task queue with idempotent handlers |
| 9–12 | Durabilize the critical path only |
| 13–20 | Durable execution is the right primitive |
Quick check — you need this if any are true:
- A crash mid-workflow means a customer gets charged but never receives the product
- Your workflow spans multiple HTTP requests or process lifetimes
- You need human approval gates that pause for hours or days
- Duplicate execution of a step causes real-world harm (double charges, duplicate emails)
- You have multi-step processes across multiple services that must all succeed or all roll back
Choose Your Path
Does your workflow need...
├─ Just crash recovery + idempotency?
│ └─ BAKED IN: add checkpointing to your existing DB. Zero infra cost.
│ See: references/BAKED-IN.md
│
├─ Fan-out parallelism, durable sleep, human-in-the-loop,
│ or cross-service coordination?
│ └─ RESONATE: single-binary server + tiny SDK. ~$5/mo on a VPS.
│ See: references/RESONATE-QUICKSTART.md
│
└─ Enterprise-scale with managed infrastructure?
└─ Temporal Cloud ($520/mo+ at scale) or AWS Step Functions.
But consider: do you actually need that complexity?
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.
- 11d ago First seen · 409 lines · 97 tokens per session scan A 4be9d839ba6d
durable-execution is a skill published in the GitHub repository resonatehq/resonate-skills (6 stars, last pushed 19d ago), licensed Apache-2.0. It adds 97 tokens to every session and 4,792 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-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.