evm-provider-event-handling

evm-provider-event-handling is a cursor rule for Cursor from MetaMask/metamask-connect-cursor-plugin. It costs 1,943 tokens per session, scanned A, original, MIT.

A set of rules for handling events from Ethereum-compatible blockchain providers and connection tools. These events report changes such as connecting, disconnecting, switching networks, or changing wallet accounts.

In plain words
What is it for?
It is for subscribing to wallet connection events, processing changed accounts and networks, typing event payloads, and handling provider or transport event timing.
Why use it?
It prevents integrations from using incorrect event names, payload formats, or assumptions about when events are emitted.

Cursor rule for Cursor

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

Good fit It is for subscribing to wallet connection events, processing changed accounts and networks, typing event payloads, and handling provider or transport event timing.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/metamask/metamask-connect-cursor-plugin/evm-provider-event-handling
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 evm-provider-event-handling

README.md
[![agentmods](https://agentmods.dev/badge/rules/metamask/metamask-connect-cursor-plugin/evm-provider-event-handling/github.svg)](https://agentmods.dev/rules/metamask/metamask-connect-cursor-plugin/evm-provider-event-handling)
Your own site
<a href="https://agentmods.dev/rules/metamask/metamask-connect-cursor-plugin/evm-provider-event-handling"><img src="https://agentmods.dev/badge/rules/metamask/metamask-connect-cursor-plugin/evm-provider-event-handling/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.

agentmods 80×15 button for evm-provider-event-handling

Your own site · 80×15
<a href="https://agentmods.dev/rules/metamask/metamask-connect-cursor-plugin/evm-provider-event-handling"><img src="https://agentmods.dev/badge/rules/metamask/metamask-connect-cursor-plugin/evm-provider-event-handling.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,943 This file is loaded in full into every session.
When invoked 1,943 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.01943 $0.01943
Opus 5 $0.00971 $0.00971
Sonnet 5 $0.00389 $0.00389
Haiku 4.5 $0.00194 $0.00194

Measured 8d ago against content hash 0a246b2ddd3c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

evm-provider-event-handling 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 8d 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/evm-provider-event-handling.mdc · 123 lines

How it starts

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

EVM Provider Event Handling

EIP-1193 Events (EVM Provider)

  • connect — fired when the provider establishes a connection; payload: { chainId: Hex; accounts: Address[] }
  • disconnect — fired when the provider loses connection; no payload
  • accountsChanged — fired when the user's accounts change; payload: string[] (array of addresses)
  • chainChanged — fired when the active chain changes; payload: string (hex chain ID, not decimal)
  • message — part of the EIP-1193 provider event type (payload: { type: string; data: unknown }), but not currently emitted by @metamask/connect-evm; don't rely on it for subscription delivery
const provider = client.getProvider();

provider.on('accountsChanged', (accounts: string[]) => {
  console.log('New accounts:', accounts);
});

provider.on('chainChanged', (chainId: string) => {
  // chainId is HEX (e.g., '0x1'), NOT decimal
  console.log('New chain:', chainId);
});

provider.on('connect', ({ chainId, accounts }: { chainId: string; accounts: string[] }) => {
  console.log('Connected to chain:', chainId, 'accounts:', accounts);
});

provider.on('disconnect', () => {
  // No payload — the event itself is the signal
  console.log('Disconnected');
});

chainChanged Payload Type

  • chainChanged emits a hex string (e.g., '0x1', '0x89'), not a decimal number
  • Never compare directly with decimal numbers: chainId === 1 will always be false
  • Convert if needed: parseInt(chainId, 16) to get the decimal chain ID
  • This is a common source of bugs — always treat chainChanged payload as a hex string

SDK eventHandlers (Client Options)

  • Configure event callbacks directly in client options via eventHandlers:
    • connect — same as EIP-1193 connect
    • disconnect — same as EIP-1193 disconnect
    • accountsChanged — same as EIP-1193 accountsChanged
    • chainChanged — same as EIP-1193 chainChanged
    • displayUri — fires with the connection URI string for QR code rendering
    • connectAndSign — fires with the signature result from connectAndSign flow
    • connectWith — fires with the result from connectWith flow

Read the full file on GitHub · 123 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. 8d ago First seen · 123 lines · 1,943 tokens per session scan A 0a246b2ddd3c

Subscribe to this mod's changes

evm-provider-event-handling 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,943 tokens to every session, about $0.0097 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