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/rules/metamask/metamask-connect-cursor-plugin/solana-integration-constraints)<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>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.01207 | $0.01207 |
| Opus 5 | $0.00603 | $0.00603 |
| Sonnet 5 | $0.00241 | $0.00241 |
| Haiku 4.5 | $0.00121 | $0.00121 |
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.
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
createSolanaClientis"MetaMask"(renamed from"MetaMask Connect"in@metamask/connect-solana1.0.0). Match on exactly"MetaMask"— do not branch on the old"MetaMask Connect"literal. - Since
@metamask/connect-solana1.0.0,createSolanaClientno 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. WalletProvidermust receivewallets={[]}— 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
createSolanaClientearly in app startup, but it does not need to resolve before the firstWalletProviderrender - If your UI depends on MetaMask already being registered, gate that UI until
createSolanaClientresolves - Since
@metamask/connect-solana1.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 separatewallet_sessionChangedevent to read accounts on cold start - Since
@metamask/connect-solana1.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, ReactuseRef, oruseMemo— do not callgetWallet()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
invokeMethodandconnect
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 · 57 lines · 1,207 tokens per session scan A 4bf43c8d6206
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.
Other cursor rules, from other repositories
zama-protocol-zama-solidity--setups-foundry
Detailed reference for foundry (zama-solidity skill).
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…
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 │ └─────────────────┘…
solana_core_architecture
┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐ │ Entry Point │ │ Instruction │ │ Account │ │ lib.rs │───▶│ Processing │───▶│ Validation │ │ │ │ │ │ │ │ - entrypoint! │ │ - Route dispatch │ │ - Owner checks │ │ - processinst │ │ - Deserialize │ │ - Data validate │.
stacks-development
Guidelines for Stacks blockchain development.
solana_monitoring_analytics
Solana blockchain development, production monitoring, analytics, and observability.