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-async-await-engine-typescriptgit 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-async-await-engine-typescript)<a href="https://agentmods.dev/skills/resonatehq/resonate-skills/resonate-async-await-engine-typescript"><img src="https://agentmods.dev/badge/skills/resonatehq/resonate-skills/resonate-async-await-engine-typescript/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-async-await-engine-typescript"><img src="https://agentmods.dev/badge/skills/resonatehq/resonate-skills/resonate-async-await-engine-typescript.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.00093 | $0.02023 |
| Opus 5 | $0.00046 | $0.01012 |
| Sonnet 5 | $0.00019 | $0.00405 |
| Haiku 4.5 | $0.00009 | $0.00202 |
Grade A, and why
resonate-async-await-engine-typescript 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resonate Async/Await Engine (TypeScript)
SDK version: This skill reflects
@resonatehq/sdkv0.11.4 (current on npm). The async/await engine was introduced in v0.11.0.
Overview
The TypeScript SDK ships two execution engines:
| Engine | Import path | Function style | Release |
|---|---|---|---|
| Generator engine | @resonatehq/sdk |
function* / yield* |
v0.10.x and earlier; still current |
| Async/await engine | @resonatehq/sdk/async |
async function / await |
v0.11.0+ |
Both engines connect to the same Resonate Server, share the same durable-promise substrate, and support the same patterns (fan-out, human-in-the-loop, saga, etc.). The async engine is opt-in — existing generator-engine code is unaffected.
For the generator engine, see resonate-basic-ephemeral-world-usage-typescript and resonate-basic-durable-world-usage-typescript.
When to use the async engine
- Writing new TypeScript workflows and prefer
async/awaitoverfunction*/yield* - Integrating Resonate into a codebase that already uses
async/awaitthroughout - Browser or edge environments:
@resonatehq/sdk/asyncexports are browser-compatible
When to keep the generator engine
- Existing generator-engine code — there is no reason to migrate; the generator engine is fully supported
- You need
ctx.detached()with the full bounded-replay pattern (async engine also hasdetach()but check the SDK changelog for your version)
Installation
npm install @resonatehq/[email protected]
Both engines are in the same package. The generator engine is the default export; the async engine is the /async sub-export.
Basic usage
import { Resonate } from "@resonatehq/sdk/async";
const resonate = new Resonate({ url: "http://localhost:8001" });
// Register an async function
resonate.register("greet", async (ctx, name: string) => {
return `Hello, ${name}!`;
});
// Start a workflow — resonate.run(id, funcOrName, ...args) → Promise<ResonateHandle<T>>
const handle = await resonate.run("greet-001", "greet", "world");
// Await the result via the durable-promise subscription
const result = await handle.result();
// result === "Hello, world!"
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 · 223 lines · 93 tokens per session scan A 7d799808088b
resonate-async-await-engine-typescript is a skill published in the GitHub repository resonatehq/resonate-skills (6 stars, last pushed 21d ago), licensed Apache-2.0. It adds 93 tokens to every session and 2,023 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
nestjs-expert
Provides NestJS patterns for modules, controllers, providers, guards, interceptors, and microservices. Use when working with NestJS TypeScript files (.module.ts, .controller.ts, .service.ts) or when the user mentions NestJS, Nest.js, or NestJS modules.
adapter-express
Mount tRPC as Express middleware with createExpressMiddleware() from @trpc/server/adapters/express. Access Express req/res in createContext via CreateExpressContextOptions. Mount at a path prefix like app.use('/trpc', ...). Avoid global express.json() conflicting with tRPC body parsing for FormData.
trpc-router
Entry point for all tRPC skills. Decision tree routing by task: initTRPC.create(), t.router(), t.procedure, createTRPCClient, adapters, subscriptions, React Query, Next.js, links, middleware, validators, error handling, caching, FormData.
stripe-projects
Use after E2B sandbox/API access has been provisioned through Stripe Projects and the user needs to use the resulting E2B API key with the E2B CLI, JavaScript SDK, Python SDK, or Code Interpreter SDK.
nestjs-expert
Creates and configures NestJS modules, controllers, services, DTOs, guards, and interceptors for enterprise-grade TypeScript backend applications. Use when building NestJS REST APIs or GraphQL services, implementing dependency injection, scaffolding modular architecture, adding JWT/Passport authentication, integrating…
azure-web-pubsub-ts
Build real-time messaging applications using Azure Web PubSub SDKs for JavaScript (@azure/web-pubsub, @azure/web-pubsub-client). Use when implementing WebSocket-based real-time features, pub/sub me...