solana-integration-constraints

solana-integration-constraints is a cursor rule for Cursor from MetaMask/metamask-connect-cursor-plugin. It costs 1,207 tokens per session, scanned A, original, MIT.

A set of rules for connecting a Solana app to MetaMask Connect, including wallet discovery, network identifiers, supported platforms, and RPC routing. Solana is a blockchain network, and RPC services provide access to it.

In plain words
What is it for?
Configuring Solana wallet adapters, recognising MetaMask correctly, setting supported networks, routing RPC requests, and handling platform limitations.
Why use it?
It prevents duplicate wallet entries and incorrect assumptions about provider setup, networks, or platform support.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit Configuring Solana wallet adapters, recognising MetaMask correctly, setting supported networks, routing RPC requests, and handling platform limitations.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/metamask/metamask-connect-cursor-plugin/solana-integration-constraints
Install

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.

Clone the repo
git clone --depth 1 https://github.com/MetaMask/metamask-connect-cursor-plugin

Made for: Cursor.

Wrote 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.

agentmods badge for solana-integration-constraints

README.md
[![agentmods](https://agentmods.dev/badge/rules/metamask/metamask-connect-cursor-plugin/solana-integration-constraints.svg)](https://agentmods.dev/rules/metamask/metamask-connect-cursor-plugin/solana-integration-constraints)
Your own site
<a href="https://agentmods.dev/rules/metamask/metamask-connect-cursor-plugin/solana-integration-constraints"><img src="https://agentmods.dev/badge/rules/metamask/metamask-connect-cursor-plugin/solana-integration-constraints.svg" alt="Measured on agentmods" height="20"></a>
Per session 1,207 This file is loaded in full into every session.
When invoked 1,207 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01207 $0.01207
Opus 5 $0.00603 $0.00603
Sonnet 5 $0.00241 $0.00241
Haiku 4.5 $0.00121 $0.00121

Measured 7d ago against content hash 4bf43c8d6206, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

solana-integration-constraints 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.

rules/solana-integration-constraints.mdc · 57 lines

How it starts

The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Solana Integration Constraints

Wallet Adapter Configuration

  • The wallet name registered by createSolanaClient is "MetaMask" (renamed from "MetaMask Connect" in @metamask/connect-solana 1.0.0). Match on exactly "MetaMask" — do not branch on the old "MetaMask Connect" literal.
  • Since @metamask/connect-solana 1.0.0, createSolanaClient no longer announces its own wallet-standard provider if an injected Solana provider (e.g. the MetaMask browser extension) is already present. Treat the already-injected provider as MetaMask; your UI should not expect two wallet entries.
  • WalletProvider must receive wallets={[]} — MetaMask uses the wallet-standard auto-discovery protocol
  • Never manually add MetaMask to the wallets array — it will not be found and may cause duplicates
  • Initialize createSolanaClient early in app startup, but it does not need to resolve before the first WalletProvider render
  • If your UI depends on MetaMask already being registered, gate that UI until createSolanaClient resolves
  • Since @metamask/connect-solana 1.1.0, createSolanaClient() eagerly initializes the Solana wallet provider during creation — if the underlying multichain session already contains Solana scopes, the provider's accounts are populated by the time the client resolves. Apps no longer need to wait for a separate wallet_sessionChanged event to read accounts on cold start
  • Since @metamask/connect-solana 1.1.0, getWallet() returns the same wallet instance on every call instead of constructing a new one. It is safe to cache the result in a module-level constant, React useRef, or useMemo — do not call getWallet() on every render expecting a fresh instance

CAIP-2 Genesis Hash Identifiers

  • Solana mainnet: solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp
  • Solana devnet: solana:EtWTRABZaYq6iMfeYKouRu166VU2xqa1
  • These are genesis hash identifiers, not cluster URLs or chain IDs
  • Always use the full CAIP-2 string as the scope in multichain invokeMethod and connect

Read the full file on GitHub · 57 lines

Changes

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.

  1. 7d ago First seen · 57 lines · 1,207 tokens per session scan A 4bf43c8d6206

Subscribe to this mod's changes

solana-integration-constraints is a cursor rule published in the GitHub repository MetaMask/metamask-connect-cursor-plugin (2 stars, last pushed 2mo ago), licensed MIT. It adds 1,207 tokens to every session, about $0.0060 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.

Related

Other cursor rules, from other repositories

zama-protocol-zama-solidity--setups-foundry

Detailed reference for foundry (zama-solidity skill).

zama-ai/skills · 12 tokens

cardano-mcp

These rules complement our main development collaboration rules, focusing specifically on the Model Context Protocol (MCP) server project with TypeScript. This project serves as a specialized RAG (Retrieval-Augmented Generation) gateway to existing Cardano resources, documentation, and tools to assist with dApp…

Jimmyh-world/Cardano_MCP · 3,030 tokens

elizaos_v2_onchain_plugins

┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐ │ Wallet Provider│ │ Connection Mgmt │ │ Transaction Svc │ │ - Private Keys │───▶│ - RPC Endpoints │───▶│ - Tx Construction│ │ - Public Keys │ │ - Network Config │ │ - Fee Estimation│ │ - Signatures │ │ - Health Check │ │ - Broadcasting │ └─────────────────┘…

AIFlowML/cursor_rules · 0 tokens

solana_core_architecture

┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐ │ Entry Point │ │ Instruction │ │ Account │ │ lib.rs │───▶│ Processing │───▶│ Validation │ │ │ │ │ │ │ │ - entrypoint! │ │ - Route dispatch │ │ - Owner checks │ │ - processinst │ │ - Deserialize │ │ - Data validate │.

AIFlowML/cursor_rules · 4 tokens

stacks-development

Guidelines for Stacks blockchain development.

Mcsavvy/stacks-next-template-chainhooks-with-db · 7 tokens

solana_monitoring_analytics

Solana blockchain development, production monitoring, analytics, and observability.

Datai-Network/datai-mcp-server · 13 tokens