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 kaankacar/soroban-diagnose --skill skillgit clone --depth 1 https://github.com/kaankacar/soroban-diagnoseWrote 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/kaankacar/soroban-diagnose/skill)<a href="https://agentmods.dev/skills/kaankacar/soroban-diagnose/skill"><img src="https://agentmods.dev/badge/skills/kaankacar/soroban-diagnose/skill/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/kaankacar/soroban-diagnose/skill"><img src="https://agentmods.dev/badge/skills/kaankacar/soroban-diagnose/skill.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.00046 | $0.00961 |
| Opus 5 | $0.00023 | $0.00481 |
| Sonnet 5 | $0.00009 | $0.00192 |
| Haiku 4.5 | $0.00005 | $0.00096 |
Grade A, and why
soroban-diagnose 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 10d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diagnosing failed Soroban transactions
This skill wraps soroban-diagnose, a deterministic (no-LLM) resolver that
turns a failed transaction/simulation into one normalized diagnosis envelope:
the error at each of the five layers, ranked probable causes with evidence
from live ledger state, and concrete fix + verify commands.
Decision tree
- You have a transaction hash (64 hex chars):
soroban-diagnose tx <hash> --network <testnet|mainnet|futurenet> - You have a
simulateTransactionresponse (JSON): save it to a file and pass the transaction you simulated too — it unlocks state-lookup evidence:soroban-diagnose sim --file sim.json --request-xdr <envelope-b64> --network testnet - You have raw base64 XDR (a
TransactionResultfrom a sendTransaction ERROR, aTransactionEnvelope,TransactionMeta, or aDiagnosticEvent):soroban-diagnose xdr <base64> --network testnet - You only need a contract error code decoded (
Error(Contract, #N)):soroban-diagnose resolve-error <C...contract-id> <N> --network testnet
Prefer the MCP server when it is registered (soroban-diagnose-mcp): call the
diagnose_failure tool with the same inputs, or resolve_contract_error for
bare codes. Default responses are compact (~1k tokens); pass verbose: true
only when the compact evidence is insufficient.
Reading the envelope
error.id— stable namespaced identity (soroban.contract.error,soroban.host.budget.exceeded_limit,tx.bad_seq); match on this, not on prose.error.contract_error.name—Error(Contract, #7)resolved to its enum variant via the deployed wasm's spec.resolved_from: nullmeans it genuinely cannot be named (no spec / out of range) — do not invent a name.diagnoses[]— ranked causes.confirmed: truemeans a state lookup verified the hypothesis; confidence ≤ 0.5 means unverified hypothesis. Relay the top cause'sexplanation,fix.summary, andfix.commandsto the user; mention runner-ups only if the top is unconfirmed.unresolved[]— honest gaps (no rule matched, missing diagnostics, RPC unavailable). If diagnoses is empty, report the extracted layers and the unresolved reasons instead of guessing.
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.
- 10d ago First seen · 77 lines · 46 tokens per session scan A 04c46dcc70d7
soroban-diagnose is a skill published in the GitHub repository kaankacar/soroban-diagnose (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 46 tokens to every session and 961 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
code-changes
Orchestration workflow for any task that ends in code changes: issue analysis, pull request review, feature implementation, bug fixes, refactors, or fleshing out an idea. MUST be invoked at the start of such a task, before reading or writing any code. Defines how to analyze first, gate on user approval, plan, pick the…
nostr-addressable-event-dual-tag-query
Fix "count shows X but list shows empty" bugs when querying related events (comments, reactions, zaps, reposts) for Nostr addressable events (Kind 30000-39999). Use when: (1) REST API shows engagement count > 0 but WebSocket query returns empty, (2) Comments/reactions exist but app shows "No comments yet" or similar…
nostr-replaceable-event-mutation-overwrite
Fix silent data loss when mutating Nostr replaceable events (Kind 0 profile, Kind 3 contact/follow list, Kind 10002 relay list, etc.) in client apps. Use when: (1) Following someone wipes the user's entire follow list, (2) Updating profile metadata loses existing fields, (3) Fresh browser session or mobile login…
divine-relay-video-requirements
Fix "blocked: event rejected by relay policy" errors when publishing Kind 34236 (video) events to divine relays. Use when: (1) Kind 0 profile events succeed but Kind 34236 fails, (2) Generic policy rejection with no specific reason, (3) Video events work on other relays but fail on divine relays. The divine relay…
ndk-operation-timeout-wrapper
Fix NDK (Nostr Dev Kit) operations hanging indefinitely when relay connections stall. Use when: (1) App freezes during fetchEvents or publish calls, (2) No timeout errors despite network issues, (3) Relay connection appears stuck, (4) Using NDK with unstable or slow relays. NDK operations have no built-in timeout …
nostr-addressable-event-d-tag-requirement
Fix duplicate Nostr events (Kind 30000+ parameterized replaceable events) caused by missing d-tag. Use when: (1) Same content appears multiple times on relay for same pubkey, (2) Events aren't being replaced/updated as expected, (3) Publishing NIP-71 video events (Kind 34236) or other addressable events and seeing…