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-gogit 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-go)<a href="https://agentmods.dev/skills/resonatehq/resonate-skills/resonate-saga-pattern-go"><img src="https://agentmods.dev/badge/skills/resonatehq/resonate-skills/resonate-saga-pattern-go/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-go"><img src="https://agentmods.dev/badge/skills/resonatehq/resonate-skills/resonate-saga-pattern-go.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.00086 | $0.02832 |
| Opus 5 | $0.00043 | $0.01416 |
| Sonnet 5 | $0.00017 | $0.00566 |
| Haiku 4.5 | $0.00009 | $0.00283 |
Grade A, and why
resonate-saga-pattern-go 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 — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resonate Saga Pattern — Go
Version note. The Go SDK's first tagged release is
0.1.0. The tag is0.1.0, notv0.1.0, sogo get …@latestdoes not resolve to it — pin the tag explicitly:go get github.com/resonatehq/[email protected]. APIs may still change before a1.0. There is no Go saga example repo yet, so all snippets use only documented SDK surface verified against the0.1.0tag source.
Overview
A saga is a long-running transaction split into discrete steps, each with a compensating action. Forward steps execute top-to-bottom; on any failure, completed compensations run bottom-to-top. Because the whole workflow body re-runs on resume, the completed []Step slice is reconstructed deterministically on replay — each ctx.Run call short-circuits its settled durable promise in the same order, so the slice is rebuilt identically before reaching the point of failure.
For the language-agnostic mental model — including choreography vs orchestration, idempotency requirements, and when not to use sagas — see resonate-saga-pattern-typescript.
When to use
- Multi-step workflow where intermediate state is visible to other systems between steps
- Each step is individually compensable (inventory hold, payment charge, shipment create)
- You need "all or nothing" consistency without a distributed 2PC transaction
- Steps span services and may take seconds to minutes each
- Compensation logic exists and is idempotent for every committed step
Basic shape
package main
import (
"context"
"errors"
"fmt"
"log"
"time"
resonate "github.com/resonatehq/resonate-sdk-go"
)
// Step is a string enum for the forward steps that have been committed.
// Using type Step string + a switch gives idiomatic Go compensation dispatch.
type Step string
const (
StepInventory Step = "inventory"
StepPayment Step = "payment"
StepShipment Step = "shipment"
)
type OrderArgs struct {
OrderID string `json:"order_id"`
}
type SagaResult struct {
Status string `json:"status"`
OrderID string `json:"order_id"`
Compensated []string `json:"compensated,omitempty"`
}
type CompensateArgs struct {
Step Step `json:"step"`
OrderID string `json:"order_id"`
}
// placeOrder is the saga orchestrator. It runs forward steps in sequence,
// tracking each committed step. On the first failure it runs compensations in
// reverse, each as its own durable ctx.Run so they are retryable.
func placeOrder(ctx *resonate.Context, args OrderArgs) (SagaResult, error) {
var completed []Step
// --- forward path ---
fInv, err := ctx.Run(reserveInventory, args.OrderID)
if err != nil {
return SagaResult{}, err
}
if err := fInv.Await(nil); err != nil {
return compensateAll(ctx, args.OrderID, completed, err)
}
completed = append(completed, StepInventory)
fPay, err := ctx.Run(chargePayment, args.OrderID)
if err != nil {
return SagaResult{}, err
}
if err := fPay.Await(nil); err != nil {
return compensateAll(ctx, args.OrderID, completed, err)
}
completed = append(completed, StepPayment)
fShip, err := ctx.Run(createShipment, args.OrderID)
if err != nil {
return SagaResult{}, err
}
if err := fShip.Await(nil); err != nil {
return compensateAll(ctx, args.OrderID, completed, err)
}
completed = append(completed, StepShipment)
return SagaResult{Status: "success", OrderID: args.OrderID}, nil
}
// compensateAll iterates completed steps in reverse and runs each compensation
// as a durable ctx.Run. Returns a SagaResult with status "failed" on success,
// or propagates the compensation error if a compensation itself fails fatally.
func compensateAll(
ctx *resonate.Context,
orderID string,
completed []Step,
forwardErr error,
) (SagaResult, error) {
_ = forwardErr // log or inspect as needed
var names []string
for i := len(completed) - 1; i >= 0; i-- {
step := completed[i]
f, err := ctx.Run(compensate, CompensateArgs{Step: step, OrderID: orderID},
resonate.RunOpts{
Timeout: 10 * time.Minute,
RetryPolicy: resonate.ExponentialRetry{
MaxAttempts: 5,
Base: 200 * time.Millisecond,
Max: 30 * time.Second,
Jitter: true,
},
},
)
if err != nil {
return SagaResult{}, fmt.Errorf("dispatch compensation for %s: %w", step, err)
}
if err := f.Await(nil); err != nil {
// A compensation that exhausts retries is a real inconsistency — log and alert.
return SagaResult{}, fmt.Errorf("compensation for %s failed: %w", step, err)
}
names = append(names, string(step))
}
return SagaResult{
Status: "failed",
OrderID: orderID,
Compensated: names,
}, nil
}
// compensate dispatches to the correct undo action via a switch on Step.
// Each branch must be idempotent — compensations may be retried.
func compensate(_ *resonate.Context, args CompensateArgs) (struct{}, error) {
switch args.Step {
case StepShipment:
// cancelShipment(args.OrderID)
return struct{}{}, nil
case StepPayment:
// refundPayment(args.OrderID)
return struct{}{}, nil
case StepInventory:
// releaseInventory(args.OrderID)
return struct{}{}, nil
default:
return struct{}{}, resonate.NewNonRetryable(
fmt.Errorf("unknown saga step %q — programming error", args.Step),
)
}
}
// Forward leaf stubs — replace with real service calls.
func reserveInventory(_ *resonate.Context, orderID string) (struct{}, error) {
_ = orderID
return struct{}{}, nil
}
func chargePayment(_ *resonate.Context, orderID string) (struct{}, error) {
_ = orderID
return struct{}{}, nil
}
func createShipment(_ *resonate.Context, orderID string) (struct{}, error) {
_ = orderID
// Simulate a transient failure to trigger compensation.
return struct{}{}, errors.New("shipment service unavailable")
}
func main() {
r, err := resonate.New(resonate.Config{URL: "http://localhost:8001"})
if err != nil {
log.Fatalf("resonate.New: %v", err)
}
defer func() { _ = r.Stop() }()
// Only the workflow needs registration; leaves reached via ctx.Run do not.
placeOrderFn, err := resonate.Register(r, "placeOrder", placeOrder)
if err != nil {
log.Fatalf("Register: %v", err)
}
h, err := placeOrderFn.Run(context.Background(), "order-1", OrderArgs{OrderID: "order-1"})
if err != nil {
log.Fatalf("Run: %v", err)
}
res, err := h.Result(context.Background())
if err != nil {
log.Fatalf("Result: %v", err)
}
fmt.Printf("saga: %+v\n", res)
}
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 · 288 lines · 86 tokens per session scan A a226f50b47b6
resonate-saga-pattern-go is a skill published in the GitHub repository resonatehq/resonate-skills (6 stars, last pushed 21d ago), licensed Apache-2.0. It adds 86 tokens to every session and 2,832 once invoked, about $0.0004 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
golang-graphql
Implements GraphQL APIs in Golang using gqlgen or graphql-go. Apply when building GraphQL servers, designing schemas, writing resolvers, handling subscriptions, or integrating GraphQL with existing Go HTTP services. Also apply when the codebase imports github.com/99designs/gqlgen or github.com/graph-gophers/graphql-go.
golang-pro
Implements concurrent Go patterns using goroutines and channels, designs and builds microservices with gRPC or REST, optimizes Go application performance with pprof, and enforces idiomatic Go with generics, interfaces, and robust error handling. Use when building Go applications requiring concurrent programming…
golang-grpc
Provides gRPC usage guidelines, protobuf organization, and production-ready patterns for Golang microservices. Use when implementing, reviewing, or debugging gRPC servers/clients, writing proto files, setting up interceptors, handling gRPC errors with status codes, configuring TLS/mTLS, testing with bufconn, or…
golang-swagger
Golang OpenAPI/Swagger documentation with swaggo/swag — annotation comments (@Summary, @Param, @Success, @Router, @Security), swag init code generation, framework integrations (gin, echo, fiber, chi, net/http), security definitions (Bearer/JWT, OAuth2, API key), and struct tags (swaggertype, enums, example…
printing-press
Set up a new integration, connector, or CLI binding for any API. Wrap or generate a ship-ready Go CLI from an OpenAPI, HAR, or Postman spec via the lean research -> generate -> build -> shipcheck loop. Use when the user says build a CLI, wrap this API, set up a new integration, add a connector, integrate with a…
goframe-v2
GoFrame development skill. TRIGGER when writing/modifying Go files, implementing services, creating APIs, or database operations. DO NOT TRIGGER for frontend/shell scripts.