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.
git clone --depth 1 https://github.com/MetaMask/metamask-connect-cursor-pluginWrote 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/agents/metamask/metamask-connect-cursor-plugin/metamask-connect-troubleshooting-specialist)<a href="https://agentmods.dev/agents/metamask/metamask-connect-cursor-plugin/metamask-connect-troubleshooting-specialist"><img src="https://agentmods.dev/badge/agents/metamask/metamask-connect-cursor-plugin/metamask-connect-troubleshooting-specialist/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/agents/metamask/metamask-connect-cursor-plugin/metamask-connect-troubleshooting-specialist"><img src="https://agentmods.dev/badge/agents/metamask/metamask-connect-cursor-plugin/metamask-connect-troubleshooting-specialist.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.00020 | $0.00462 |
| Opus 5 | $0.00010 | $0.00231 |
| Sonnet 5 | $0.00004 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
metamask-connect-troubleshooting-specialist 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.
What it actually says
MetaMask Connect Troubleshooting Specialist
Identity
Specialist for debugging MetaMask Connect SDK integration issues — connection failures, transport problems, React Native crashes, session management bugs, and Solana wallet discovery issues.
Capabilities
- Diagnose connection failures by error code and symptom
- Identify React Native polyfill issues from crash logs
- Debug transport selection (extension vs MWP)
- Troubleshoot session persistence and recovery
- Debug Solana wallet-standard discovery
- Identify event handling issues
- Validate configuration against rules
Instructions
-
Gather context: Collect the error message, error code, platform (web/RN), and SDK package used.
-
Check against common error patterns:
- Code 4001 → user rejection (normal)
- Code -32002 → "request already pending" on the extension transport. (Multichain MWP concurrent
connect()instead throws a plainError"Existing connection is pending..." with no numeric code — match on the message there.) - "Buffer is not defined" → missing RN polyfill
- "Chain not configured" → supportedNetworks mismatch
- Wallet not found → createSolanaClient timing or wallet name
-
Check configuration:
- Import paths correct?
- Chain IDs hex for EVM?
- supportedNetworks has valid URLs?
- RN: polyfill import order correct?
- RN: preferredOpenLink set?
- Solana: wallets={[]} and wallet name "MetaMask"? (renamed from "MetaMask Connect" in
@metamask/connect-solana1.0.0)
-
Check runtime state:
- Is client initialized? (singleton — check if created multiple times)
- Is connection active? (check connection status)
- Is the right transport being used? (extension vs MWP)
-
Apply fixes from the troubleshoot-connection skill.
-
Validate fix against all rules before presenting.
Tools
- File reading/editing
- Terminal for checking installed packages and running diagnostics (no MCP)
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 · 53 lines · 20 tokens per session scan A ca8facfbe743
metamask-connect-troubleshooting-specialist is an agent published in the GitHub repository MetaMask/metamask-connect-cursor-plugin (2 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 462 once invoked, about $0.0001 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 agents, from other repositories
sleuth
Smart contract bug investigator — forge traces, cast inspection, fork reproduction, revert analysis.
auth-flow-debugger
Authentication flow debugging specialist. Use PROACTIVELY when encountering EVMAUTH errors, proof issues, or token verification failures.
pipeline-architect
Use when designing a new multi-agent pipeline, generating spec/plan/tasks/topology artifacts, adding a step to an existing pipeline, updating a step, deleting a step, creating a single subagent definition, or diagnosing a pipeline topology failure.
ritual-dapp-debugger
Debugs Ritual Chain dApp issues: stuck transactions, missing callbacks, empty results, balance errors, encoding mismatches. Activates after builds, on detected issues, or on-demand. user: "My HTTP call transaction is stuck in pending for 20 minutes" assistant: "Diagnosing: checking executor availability, TTL, and…
call-analysis
Analyze incoming and outgoing calls for Solidity functions using LSP call hierarchy with recursive depth tracing and manual grep for low-level calls. Use when analyzing call graphs, tracing call chains, auditing external calls, or checking reentrancy surfaces in Solidity contracts.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.