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-durable-sleep-scheduled-work-rustgit 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-durable-sleep-scheduled-work-rust)<a href="https://agentmods.dev/skills/resonatehq/resonate-skills/resonate-durable-sleep-scheduled-work-rust"><img src="https://agentmods.dev/badge/skills/resonatehq/resonate-skills/resonate-durable-sleep-scheduled-work-rust/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-durable-sleep-scheduled-work-rust"><img src="https://agentmods.dev/badge/skills/resonatehq/resonate-skills/resonate-durable-sleep-scheduled-work-rust.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.00096 | $0.02057 |
| Opus 5 | $0.00048 | $0.01028 |
| Sonnet 5 | $0.00019 | $0.00411 |
| Haiku 4.5 | $0.00010 | $0.00206 |
Grade A, and why
resonate-durable-sleep-scheduled-work-rust 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resonate Durable Sleep + Scheduled Work — Rust
SDK note (0.6.0). The Rust SDK is in active development. This skill covers two features in the current release:
ctx.sleep(Duration)for in-workflow durable sleep, andresonate.schedule(name, cron, fn, input)for cron-registered ephemeral-world scheduling. (Note: Python'sresonate-sdk0.7.4 also has a top-levelresonate.schedule(...)now — confirmed against the installed package; see the cross-SDK asymmetry note below for what's still Rust/TypeScript-only.)
Overview
Two related but distinct capabilities:
- Durable sleep inside a workflow —
ctx.sleep(Duration)pauses execution; the worker process is free to exit and resume days later without the sleep "losing its place." - Cron-scheduled invocation from the ephemeral world —
resonate.schedule(...)registers a function to fire on a cron schedule until explicitly deleted.
Both are Rust-idiomatic — Duration for in-workflow time, cron strings for cron schedules. Both are durable; Resonate holds the continuation in its store, not in a long-running process.
Durable sleep: ctx.sleep(Duration)
use resonate::prelude::*;
use std::time::Duration;
#[resonate::function]
async fn daily_reminder(ctx: &Context, user_id: String) -> Result<()> {
loop {
ctx.sleep(Duration::from_secs(24 * 60 * 60)).await?; // 24 hours
ctx.rpc::<()>("send_reminder", user_id.clone()).await?;
}
}
No upper bound on sleep duration. The worker process can exit after the .await? — Resonate's server holds the continuation and re-dispatches when the sleep expires.
Reminder workflows
#[resonate::function]
async fn seven_day_renewal_reminder(ctx: &Context, subscription_id: String) -> Result<()> {
// 7 days before renewal
ctx.sleep(Duration::from_secs(7 * 24 * 60 * 60)).await?;
ctx.rpc::<()>("send_renewal_warning", subscription_id.clone()).await?;
// 1 day before renewal
ctx.sleep(Duration::from_secs(6 * 24 * 60 * 60)).await?;
ctx.rpc::<()>("send_final_warning", subscription_id.clone()).await?;
// renewal day
ctx.sleep(Duration::from_secs(24 * 60 * 60)).await?;
ctx.rpc::<()>("charge_renewal", subscription_id).await?;
Ok(())
}
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 · 195 lines · 96 tokens per session scan A 721d8c8ec033
resonate-durable-sleep-scheduled-work-rust is a skill published in the GitHub repository resonatehq/resonate-skills (6 stars, last pushed 21d ago), licensed Apache-2.0. It adds 96 tokens to every session and 2,057 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
golem-make-http-request-rust
Making outgoing HTTP requests from a Rust Golem agent. Use when the user asks to call an external API, make HTTP requests, use an HTTP client, or send HTTP requests from agent code.
golem-add-llm-rust
Adding LLM and AI capabilities to a Rust Golem agent. Use when the user wants to add LLM chat, embeddings, web search, vector DB, graph DB, document search, video generation, speech-to-text, text-to-speech, or any AI provider integration.
golem-parallel-workers-rust
Fan out work to multiple parallel agents and collect results in a Rust Golem project. Use when the user asks about parallel execution, fan-out/fan-in, spawning child agents for parallel work, forking, or aggregating results from multiple agents.
golem-retry-policies-rust
Configuring semantic retry policies for a Rust Golem agent. Use when the user asks about retry policies, retry strategies, exponential backoff, error handling retries, transient error recovery, retry predicates, withRetryPolicy, withnamedpolicy, NamedPolicy, Policy composition, jitter, countBox, timeBox, andThen, or…
golem-add-http-endpoint-rust
Exposing a Rust Golem agent over HTTP. Use when the user asks to add HTTP endpoints, mount an agent to a URL path, or expose agent methods as a REST API.
golem-atomic-block-rust
Using atomic blocks, idempotency, and oplog management in a Rust Golem project. Use when the user asks about atomically, idempotence mode, oplog commit, or idempotency keys.