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.
npx agentmods add rules/phantom/phantom-agent-kit/embedded-wallet-constraintsgit clone --depth 1 https://github.com/phantom/phantom-agent-kitWhat 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 | $0.00274 | $0.00274 |
| Opus 5 | $0.00137 | $0.00137 |
| Sonnet 5 | $0.00055 | $0.00055 |
| Haiku 4.5 | $0.00027 | $0.00027 |
Grade A, and why
embedded-wallet-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 2d 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
Embedded Wallet Constraints
Unsupported Methods
signTransactionandsignAllTransactionsare NOT supported for embedded wallets. Always usesignAndSendTransactioninstead. Calling unsupported methods will throw a runtime error.
Spending Limits
- Default spending limit for embedded wallets is $1,000 USD per day per app per user. Design your UX to account for this limit and provide clear error messages if a transaction exceeds it.
Session Duration
- Social login sessions persist for 7 days from the last authentication event. After expiry, users must re-authenticate. Handle session expiration gracefully in your UI — check
isConnectedbefore operations and prompt re-login when needed.
Social Login Requirements
- Social login (Google, Apple) requires a valid
appIdfrom Phantom Portal. Without anappId, social login options will not appear.
React Native Polyfill
- React Native apps MUST import
react-native-get-random-valuesas the very first import in the entry file, before any other imports including the Phantom SDK. Failing to do this will cause crypto-related runtime errors.
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.
- 2d ago First seen · 28 lines · 274 tokens per session scan A d319bbffccf4
embedded-wallet-constraints is a cursor rule published in the GitHub repository phantom/phantom-agent-kit (11 stars, last pushed 14d ago), licensed MIT. It adds 274 tokens to every session, about $0.0014 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-30.
Other cursor rules, from other repositories
general
You are part of EVM Cortex, an Ethereum protocol engineering squad with specialized agents, skills, hooks, and rules.
solana-integration-constraints
Constraints and requirements for Solana integration with MetaMask Connect — wallet adapter config, CAIP-2 IDs, network support per platform, RPC routing, and platform limitations.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.