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 agentmods add commands/solanabr/solana-ai-kit/debug-user-txgit clone --depth 1 https://github.com/solanabr/solana-ai-kitWrote 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/commands/solanabr/solana-ai-kit/debug-user-tx)<a href="https://agentmods.dev/commands/solanabr/solana-ai-kit/debug-user-tx"><img src="https://agentmods.dev/badge/commands/solanabr/solana-ai-kit/debug-user-tx.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 | $0.00023 | $0.04606 |
| Opus 5 | $0.00012 | $0.02303 |
| Sonnet 5 | $0.00005 | $0.00921 |
| Haiku 4.5 | $0.00002 | $0.00461 |
Grade A, and why
debug-user-tx scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST "$RPC" \ How it starts
The opening of the file, as written. The whole thing — 381 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are debugging a transaction that a user reports as failing. You have the project's source code locally; the goal is to reproduce the failure against forked cluster state, then map the on-chain error back to the exact line of Rust / IDL that produced it and suggest a fix.
Related Skills
- ext/solana-dev/skill/references/testing.md — Surfpool (mainnet fork), LiteSVM, Mollusk
- ext/solana-dev/skill/references/programs/anchor.md — Anchor error codes, constraint failures
- ext/solana-dev/skill/references/programs/pinocchio.md — Pinocchio error patterns
- ext/solana-dev/skill/references/security.md — Common failure categories
Inputs
Collect from the user (at least one of signature or instruction is required):
| Input | Required | Notes |
|---|---|---|
signature |
preferred | On-chain tx signature. Fastest path — fetch + replay. |
wallet |
optional | User's pubkey. Auto-extracted from tx if signature given. |
instruction |
fallback | Raw ix JSON when the tx never landed (serialized tx / accounts + data). |
cluster |
optional | mainnet / devnet. Default: infer from Anchor.toml or .env. |
rpc |
optional | Override RPC endpoint. Default: cluster default or project .env. |
program |
optional | Program ID. Auto-detected from workspace. |
If the user only pasted an error message, ask for the signature before proceeding — it's the difference between 30 seconds and guessing.
Step 1: Detect Project Layout
echo "Detecting project..."
FRAMEWORK="unknown"
if [ -f "Anchor.toml" ]; then
FRAMEWORK="anchor"
echo "Anchor project detected"
elif [ -f "Cargo.toml" ] && grep -q "pinocchio" Cargo.toml 2>/dev/null; then
FRAMEWORK="pinocchio"
echo "Pinocchio project detected"
elif [ -f "Cargo.toml" ] && grep -q "solana-program" Cargo.toml 2>/dev/null; then
FRAMEWORK="native"
echo "Native Solana program detected"
else
echo "No Solana program workspace detected. Debug will proceed RPC-only (no source mapping)."
fi
# Infer cluster
CLUSTER="${CLUSTER:-mainnet}"
if [ -f "Anchor.toml" ]; then
DETECTED=$(grep -m1 'cluster' Anchor.toml | sed 's/.*= *//' | tr -d '"')
[ -n "$DETECTED" ] && CLUSTER="$DETECTED"
fi
echo "Cluster: $CLUSTER"
# Collect program IDs + IDLs
ls target/idl/*.json 2>/dev/null || echo "No IDLs found at target/idl/ — run 'anchor build' for best results"
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.
- 4d ago First seen · 381 lines · 23 tokens per session scan A 7ce7d0431893
debug-user-tx is a command published in the GitHub repository solanabr/solana-ai-kit (98 stars, last pushed 14d ago), licensed MIT. It adds 23 tokens to every session and 4,606 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
create-hook
Create hooks with brainstorming and security-first design.
validate-hook
Validate hooks for security, performance, and SDK compliance.
evaluate-skill
Manually evaluate a recent skill execution to record qualitative feedback.
strict
Enable strict RIPER protocol enforcement.
plan
Enter PLAN mode to create detailed technical specifications.
research
Enter RESEARCH mode for information gathering.