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-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-basic-debugging-typescript)<a href="https://agentmods.dev/skills/resonatehq/resonate-skills/resonate-basic-debugging-typescript"><img src="https://agentmods.dev/badge/skills/resonatehq/resonate-skills/resonate-basic-debugging-typescript.svg" alt="Measured on agentmods" 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.00043 | $0.01123 |
| Opus 5 | $0.00022 | $0.00562 |
| Sonnet 5 | $0.00009 | $0.00225 |
| Haiku 4.5 | $0.00004 | $0.00112 |
Grade A, and why
resonate-basic-debugging-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 7d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resonate Debug and Troubleshoot
Overview
Use this skill to diagnose Resonate runtime issues in the TypeScript SDK or Resonate Server. Focus on reproducible symptoms, promise state, registration, determinism, and routing.
Triage Flow
- Classify the failure: build/type error, runtime SDK error, server error code, or workflow stuck/hanging.
- Confirm worker is running and connected to the correct server URL and group.
- Inspect the promise state and call graph for the execution ID.
- Validate registration names and serialization rules.
- Check determinism and
yield*usage inside durable functions.
CLI and Observability Tools
- Start a clean local server:
resonate dev. - Invoke a workflow:
resonate invoke <promise-id> --func <name> --arg .... - Inspect call graph:
resonate tree <promise-id>. - Inspect promise state:
resonate promises get <id>. - Search promises by state or tags:
resonate promises search <id>. - Resolve/reject external promises:
resonate promises resolve|reject <id>.
Common Symptoms and Fixes
- Function not registered (1103): ensure
registername matches invocation name. - Function already registered (1102): avoid duplicate names or versions in one process.
- Args unencodeable (1106): pass only serializable args to RPC or top-level invocations.
- Promise already exists (40900): expected for idempotency; change the ID when you want a fresh run.
- Promise not found (40400): wrong ID or wrong server URL.
- Promise already resolved/rejected/timed out (40300-40303): treat as idempotency; pick a new ID or handle as cached result.
- Workflow hangs: target group mismatch, no active workers, or missing
yield*before awaiting a future. - Unexpected replays: expected after each checkpoint; avoid side effects outside
ctx.run.
Code Examples
Minimal repro (worker)
// worker.ts
import { Resonate, type Context } from "@resonatehq/sdk";
const resonate = new Resonate({ url: "http://localhost:8001", group: "worker" });
function* ping(_: Context, name: string) {
return `pong ${name}`;
}
resonate.register("ping", ping);
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.
- 7d ago First seen · 153 lines · 43 tokens per session scan A a84e6b92fbbb
resonate-basic-debugging-typescript is a skill published in the GitHub repository resonatehq/resonate-skills (6 stars, last pushed 15d ago), licensed Apache-2.0. It adds 43 tokens to every session and 1,123 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
cli-wiring
Bug class: Commands implemented in packages/squad-cli/src/cli/commands/ but never routed in cli-entry.ts.
agents-sdk-typescript-debugging
Use when troubleshooting an agent built with the Microsoft Agents SDK (@microsoft/agents-hosting and related packages). Trigger on any of these symptoms: build or TypeScript errors, crashes on startup, 401 or auth errors on incoming requests, the bot not responding to messages, .env configuration problems, Azure AD…
node-modules-inspector
Inspects a project's installed nodemodules and produces three reports: duplicated packages (installed in multiple versions), packages sorted by install size, and maintenance actions (dep-upgrade opportunities + publint findings, grouped by consumer/author). Use when the user wants to audit dependencies, find duplicate…
config
How to author a kubb.config.ts and pick the right @kubb/plugin- packages when generating TypeScript from an OpenAPI/Swagger spec. Use whenever setting up Kubb, adding a generator, or debugging codegen output.
agent-inspect
Local evidence debugger and trajectory-test toolkit for TypeScript AI agents. Use when capturing framework-faithful traces, asserting TraceContract/TraceFacts, packaging Evidence v2, or inspecting local runs over read-only MCP (gettracefacts).
mintlify-api
Interact with the Mintlify REST API to manage deployments, trigger builds, and query documentation site metadata programmatically.