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-external-system-of-record-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-external-system-of-record-pattern-go)<a href="https://agentmods.dev/skills/resonatehq/resonate-skills/resonate-external-system-of-record-pattern-go"><img src="https://agentmods.dev/badge/skills/resonatehq/resonate-skills/resonate-external-system-of-record-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-external-system-of-record-pattern-go"><img src="https://agentmods.dev/badge/skills/resonatehq/resonate-skills/resonate-external-system-of-record-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.00088 | $0.03181 |
| Opus 5.5 | $0.00035 | $0.01272 |
| Sonnet 5.5 | $0.00018 | $0.00636 |
| Haiku 4.5 | $0.00009 | $0.00318 |
Grade A, and why
resonate-external-system-of-record-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 2mo 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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resonate External System of Record 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 system-of-record example repo yet, so all snippets use only documented SDK surface verified against the0.1.0tag source.
Overview
For the language-agnostic framing and the "Write Last, Read First" mental model, see resonate-external-system-of-record-pattern-typescript. This skill translates that model to idiomatic Go: explicit (T, error) returns, option structs, and ctx.Run-based checkpointing without a separate dependency-injection mechanism.
The core contract is simple: one system owns the truth. Resonate coordinates the workflow and guarantees at-least-once execution; the external system enforces consistency through its own primitives — idempotency keys, upserts, conditional writes, ledger deduplication.
When to use
- A Resonate workflow must create, update, or read from a database, payment processor, ledger, or any external store that has its own durability.
- You need multi-step operations (reserve → charge → record) to be safe to retry without double-writes.
- You cannot use distributed transactions across Resonate's promise store and the external system.
Do not use this pattern when all writes live inside a single ACID transaction scope — just use the transaction.
The replay principle — wrap every SoR call in ctx.Run
This is the entire reason the pattern exists.
Whenever a workflow suspends and resumes (after a ctx.Sleep, a remote ctx.RPC, or a pending ctx.Promise), the entire workflow body re-executes from the top. Durable child promises short-circuit steps that already settled — the external call is not re-fired, and the stored result is returned directly. But any external call that is NOT wrapped in a ctx.Run will execute again on every replay, producing double-writes.
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.
- 2mo ago First seen · 278 lines · 88 tokens per session scan A 4232f4c390c7
resonate-external-system-of-record-pattern-go is a skill published in the GitHub repository resonatehq/resonate-skills (7 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 88 tokens to every session and 3,181 once invoked, about $0.0004 per session on Opus 5.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-add-config-go
Adding typed configuration to a Go Golem agent with DefineConfiguredAgent and ctx.Config. Use when the user asks about agent config, configuration values, config structs, or passing settings to a Go agent.
golem-add-http-endpoint-go
Exposing a Go agent's methods over HTTP. Use when the user wants to add an HTTP endpoint/route to an agent, mount an agent under a URL path, make agent methods callable over HTTP, or map path/query/header parameters in a Go Golem project.
golem-http-router-go
Handling raw HTTP requests in Go with an HTTP router — mounting a net/http handler (ServeMux or any router), streaming request and response bodies, serving static files, and providing an OpenAPI document. Use when the user wants custom HTTP handling, to port an existing net/http service, to serve a website or files…
golem-make-http-request-go
Making outgoing HTTP requests from a Go agent. Use when the user wants an agent to call an external API/service, fetch a URL, or make an outbound HTTP/HTTPS request in a Go Golem project.
golem-mark-read-only-go
Marking Go agent methods as read-only for a side-effect-free guarantee and result caching. Use when the user wants a cacheable query method, a method that must not do remote side effects, or HTTP GET endpoints backed by a read-only method in a Go Golem project.
golem-add-cors-go
Configuring CORS on a Go agent's HTTP endpoints. Use when the user asks to enable CORS, allow cross-origin requests, or configure allowed origins for HTTP endpoints in a Go Golem project.