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-basic-debugging-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-basic-debugging-go)<a href="https://agentmods.dev/skills/resonatehq/resonate-skills/resonate-basic-debugging-go"><img src="https://agentmods.dev/badge/skills/resonatehq/resonate-skills/resonate-basic-debugging-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-basic-debugging-go"><img src="https://agentmods.dev/badge/skills/resonatehq/resonate-skills/resonate-basic-debugging-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.00083 | $0.02962 |
| Opus 5.5 | $0.00033 | $0.01185 |
| Sonnet 5.5 | $0.00017 | $0.00592 |
| Haiku 4.5 | $0.00008 | $0.00296 |
Grade A, and why
resonate-basic-debugging-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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resonate Basic Debugging — 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. Every code block here is verified against the0.1.0tag source and theresonatehq-examples/*-gorepos.
Overview
Go's type system catches some bugs at compile time, but several Go-specific traps only surface at workflow-execution time. The most dangerous ones are silent: wrong leaf signatures, bad promise encoding, and r.Stop() on a live worker all fail without a clear error at the point of mistake. This skill is a symptom-first guide to those failure modes.
For the language-agnostic replay and recovery mental model, read durable-execution first.
Triage flow
- Is the worker connected? Confirm
resonate.Newdid not return an error and that the correctURL/Networkis set. - Is the function registered?
resonate.Registerreturns(RegisteredFunc, error)— unwrap and log. - Is the promise stuck? Run
resonate promise get <id>to check state (pending/resolved/rejected/timedout). - Is the workflow replaying but producing duplicates? An un-checkpointed side effect is re-running above a durable boundary.
- Does
Future.Awaitreturn a decode error after external settlement? Likely aresonate.NewValueencoding mismatch. - Is the worker up but not picking up work?
r.Stop()may have been called on a live worker.
Stuck / never-resuming workflows
Latent promise never settled
Symptom: Future.Await blocks indefinitely; resonate promise get <id> shows state pending.
Causes:
- The external actor never called
Promises().Resolve/PromiseSettle/resonate promise resolve <id>. - The promise was settled but the value encoding is wrong —
Future.Awaitfails with a decode error and the workflow re-suspends.
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 · 249 lines · 83 tokens per session scan A c4760ef9f691
resonate-basic-debugging-go is a skill published in the GitHub repository resonatehq/resonate-skills (7 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 83 tokens to every session and 2,962 once invoked, about $0.0003 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-logging-go
Structured logging from a Go Golem agent via log/slog. Use when the user asks about logging, log levels, structured/key-value logs, or printing debug/info/error output from a Go agent.
stack-trace-go-probe
Internal helper for meta-stack-trace-investigator. Use when a Go panic or stack trace needs Go-specific nil/error checks, go test reproducer guidance, and patch targets.
golang-troubleshooting
Troubleshoot Golang programs systematically - find and fix the root cause. Use when encountering bugs, crashes, deadlocks, races, or unexpected behavior in Go code. Covers debugging methodology, common Go pitfalls, test-driven debugging, pprof setup and capture, Delve, race detection, GODEBUG tracing, and production…
golang-error-handling
Idiomatic Golang error handling — creation, wrapping with %w, errors.Is/As, errors.Join, custom error types, sentinel errors, panic/recover, the single handling rule, structured logging with slog, HTTP request logging middleware, and samber/oops for production errors. Built to make logs usable at scale with log…
tree-sitter-language-pack-extracting-code-structure
Use when the user wants structured code metadata from a source file — functions, classes, imports, exports, symbols, docstrings, comments, or syntax diagnostics. Covers ts-pack process feature flags, the JSON result shape, and the default feature set.
tree-sitter-language-pack-parsing-source
Use when the user wants a tree-sitter syntax tree for a source file — an s-expression dump or JSON tree. Covers ts-pack parse, language auto-detection vs --language, stdin input, and reading haserrors.