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/multichain-session-lifecycle)<a href="https://agentmods.dev/rules/metamask/metamask-connect-cursor-plugin/multichain-session-lifecycle"><img src="https://agentmods.dev/badge/rules/metamask/metamask-connect-cursor-plugin/multichain-session-lifecycle/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/rules/metamask/metamask-connect-cursor-plugin/multichain-session-lifecycle"><img src="https://agentmods.dev/badge/rules/metamask/metamask-connect-cursor-plugin/multichain-session-lifecycle.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.01827 | $0.01827 |
| Opus 5.5 | $0.00731 | $0.00731 |
| Sonnet 5.5 | $0.00365 | $0.00365 |
| Haiku 4.5 | $0.00183 | $0.00183 |
Grade A, and why
multichain-session-lifecycle 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 1mo 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multichain Session Lifecycle
Singleton Merging
createMultichainClientis a singleton — calling it multiple times returns the same instance- On subsequent calls, new options merge into the existing instance
- The
dappobject from the first call is used for the client's lifetime — it is excluded from option merging entirely (laterdappvalues are ignored) api.supportedNetworksentries merge by spreading the new map over the old — new chains are added and existing keys are overwritten by later calls- Call
createMultichainClientonce at app startup and store the returned client reference
Concurrent Connect Guard
- Only one
connect()call can be active at a time over MetaMask Wallet Protocol (MWP) - Calling
connect()while a previous MWPconnect()is pending throws a plainError("Existing connection is pending. Please check your MetaMask Mobile app to continue.") with no numeric code — match on the message. (-32002is an extension-transport RPC-queue code, not an SDK error code) - Guard against double-clicks with a loading state or disable the connect button during connection
- The original pending
connect()promise will resolve once the user acts in MetaMask
Session Data Shape
- Multichain
connect()resolves with no value (Promise<void>) — session data arrives via thewallet_sessionChangedevent or on demand fromclient.provider.getSession() - Session data is
SessionData: scopes live undersessionScopes(e.g.,session.sessionScopes['eip155:1'].accounts), and accounts are CAIP-10 strings (eip155:1:0x...) sessionPropertiesmay be present — if empty, it isundefined(not an empty object)- Always null-check
sessionPropertiesbefore accessing its fields - Since
@metamask/connect-evm1.2.0, everywallet_createSessionrequest issued byconnect-evmattachessessionProperties: { 'eip1193-compatible': true }. Sessions established throughcreateEVMClientwill surface this flag on the resolved session, letting wallets and analytics consumers distinguish EIP-1193-style connections from pure Multichain API connections or other provider types (e.g. Solana Wallet Standard). Do not rely on it being present for sessions created directly via the multichain client
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.
- 1mo ago First seen · 98 lines · 1,827 tokens per session scan A 3e706b81b186
multichain-session-lifecycle is a cursor rule published in the GitHub repository MetaMask/metamask-connect-cursor-plugin (2 stars, last pushed 28d ago), licensed MIT. It adds 1,827 tokens to every session, about $0.0073 per session on Opus 5.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.