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-saga-pattern-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-saga-pattern-typescript)<a href="https://agentmods.dev/skills/resonatehq/resonate-skills/resonate-saga-pattern-typescript"><img src="https://agentmods.dev/badge/skills/resonatehq/resonate-skills/resonate-saga-pattern-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-saga-pattern-typescript"><img src="https://agentmods.dev/badge/skills/resonatehq/resonate-skills/resonate-saga-pattern-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.00037 | $0.04486 |
| Opus 5 | $0.00018 | $0.02243 |
| Sonnet 5 | $0.00007 | $0.00897 |
| Haiku 4.5 | $0.00004 | $0.00449 |
Grade A, and why
resonate-saga-pattern-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 — 685 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resonate Saga Pattern (TypeScript)
Overview
The Saga pattern coordinates long-running distributed transactions by breaking them into smaller, isolated steps with compensating actions. If any step fails, the saga executes compensation logic to undo completed steps, maintaining eventual consistency without distributed locks or two-phase commits.
Core principle: Each step has a forward action (transaction) and a compensating action (rollback). On failure, compensations execute in reverse order to restore consistency.
Mental Model
Forward Execution (Happy Path):
Step 1 → Step 2 → Step 3 → Success
Failure with Compensation:
Step 1 ✓ → Step 2 ✓ → Step 3 ✗
↓
Compensate 2 → Compensate 1 → Saga Failed (Consistent)
Basic Saga Structure
function* sagaWorkflow(ctx: Context, orderId: string) {
const completedSteps: string[] = [];
try {
// Step 1: Reserve inventory
yield* ctx.run(reserveInventory, orderId);
completedSteps.push("inventory");
// Step 2: Charge payment
yield* ctx.run(chargePayment, orderId);
completedSteps.push("payment");
// Step 3: Create shipment
yield* ctx.run(createShipment, orderId);
completedSteps.push("shipment");
return { status: "success", orderId };
} catch (error) {
// Compensate in reverse order
for (const step of completedSteps.reverse()) {
yield* ctx.run(compensate, step, orderId);
}
return { status: "failed", orderId, compensated: completedSteps };
}
}
async function compensate(_ctx: Context, step: string, orderId: string) {
switch (step) {
case "shipment":
await cancelShipment(orderId);
break;
case "payment":
await refundPayment(orderId);
break;
case "inventory":
await releaseInventory(orderId);
break;
}
}
Pattern Variants
1. Explicit Compensation Functions
interface SagaStep<T> {
name: string;
action: (ctx: Context, data: T) => Generator;
compensate: (ctx: Context, data: T) => Generator;
}
function* genericSaga<T>(ctx: Context, steps: SagaStep<T>[], data: T) {
const completed: SagaStep<T>[] = [];
try {
for (const step of steps) {
yield* step.action(ctx, data);
completed.push(step);
}
return { status: "success" };
} catch (error) {
console.error(`Saga failed at step ${completed.length + 1}:`, error);
// Compensate in reverse
for (const step of completed.reverse()) {
try {
yield* step.compensate(ctx, data);
} catch (compensateError) {
console.error(`Compensation failed for ${step.name}:`, compensateError);
// Log but continue compensating other steps
}
}
return { status: "failed", error, compensated: completed.map(s => s.name) };
}
}
// Usage
function* orderSaga(ctx: Context, order: Order) {
const steps: SagaStep<Order>[] = [
{
name: "inventory",
action: function* (ctx, order) {
yield* ctx.run(reserveInventory, order.id);
},
compensate: function* (ctx, order) {
yield* ctx.run(releaseInventory, order.id);
}
},
{
name: "payment",
action: function* (ctx, order) {
yield* ctx.run(chargePayment, order.id, order.total);
},
compensate: function* (ctx, order) {
yield* ctx.run(refundPayment, order.id);
}
},
{
name: "shipment",
action: function* (ctx, order) {
yield* ctx.run(createShipment, order.id);
},
compensate: function* (ctx, order) {
yield* ctx.run(cancelShipment, order.id);
}
}
];
return yield* genericSaga(ctx, steps, order);
}
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 · 685 lines · 37 tokens per session scan A 68cf26905338
resonate-saga-pattern-typescript is a skill published in the GitHub repository resonatehq/resonate-skills (6 stars, last pushed 21d ago), licensed Apache-2.0. It adds 37 tokens to every session and 4,486 once invoked, about $0.0002 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...