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 instructions/phantom/phantom-agent-kit/claude-mdgit 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.00680 | $0.00680 |
| Opus 5 | $0.00340 | $0.00340 |
| Sonnet 5 | $0.00136 | $0.00136 |
| Haiku 4.5 | $0.00068 | $0.00068 |
Grade A, and why
phantom-agent-kit CLAUDE.md 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.
How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phantom Connect
Give your agent a wallet. Swap, sign, and manage addresses across Phantom's supported chains — and tap into Phantom's docs for context. This plugin also includes skills, rules, and agents to help scaffold wallet-connected apps with the Phantom Connect SDK across React, React Native, and vanilla JS/TS.
Works with both Cursor and Claude Code.
Skill
Use /phantom-connect to activate the Phantom Connect skill. It covers all three SDKs (React, React Native, Browser), transaction patterns, payments, token-gating, and NFT minting.
SDK Rules
Phantom SDK Best Practices
- Always use
signAndSendTransactionfor sending transactions. NEVER usesignTransaction— it is NOT supported for embedded wallets. - In React apps, wrap the application root in
PhantomProviderwith a valid config (appId,providers,addressTypes). - In vanilla JS/TS apps, initialize a single
BrowserSDKinstance as a singleton. Never create multiple instances. - Wrap
connect(),signAndSendTransaction(),signMessage(), and other async SDK calls in try-catch blocks. - Check
isConnectedbefore signing or transaction operations. - Import
AddressTypefrom@phantom/browser-sdkonly. - Register your app in Phantom Portal and use a real
appId.
Solana Transaction Safety
- Always use
LAMPORTS_PER_SOLfrom@solana/web3.jsfor SOL-to-lamport conversion. Never hardcode1000000000. - For time-sensitive transactions, add priority fees with
ComputeBudgetProgram.setComputeUnitPrice(). - Verify transaction status after sending with
connection.getSignatureStatus()orconnection.confirmTransaction(). - Use devnet (
https://api.devnet.solana.com) for testing, mainnet-beta (https://api.mainnet-beta.solana.com) for production. - Never expose private keys in code. Never ask users to input seed phrases or private keys.
Embedded Wallet Constraints
signTransactionandsignAllTransactionsare NOT supported for embedded wallets. Always usesignAndSendTransaction.- Default spending limit: $1,000 USD per day per app per user.
- Social login sessions persist 7 days from the last auth event. Handle session expiration gracefully.
- Social login (Google, Apple) requires a valid
appIdfrom Phantom Portal. - React Native apps MUST import
react-native-get-random-valuesas the very first import, before anything else.
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 · 45 lines · 680 tokens per session scan A b6c80cec7992
phantom-agent-kit CLAUDE.md is an instructions file published in the GitHub repository phantom/phantom-agent-kit (11 stars, last pushed 14d ago), licensed MIT. It adds 680 tokens to every session, about $0.0034 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 instructions, from other repositories
vibetunnel CLAUDE.md
Instructions for amantus-ai/vibetunnel, covering claude.md, project overview, common development commands, building the project and first, ensure poltergeist is running in the project root.
serve-sim AGENTS.md
Instructions for EvanBacon/serve-sim, covering native build notes, e2e testing with agent-browser and e2e testing via the serve-sim cli.
vibetunnel AGENTS.md
Instructions for amantus-ai/vibetunnel, a project described as: Turn any browser into your terminal & command your agents on the go.
BossConsole AGENTS.md
Instructions for risa-labs-inc/BossConsole, covering agents.md, project overview, essential commands, workflow rules and running commands in a visible terminal pane.
metamask-mobile CLAUDE.md
Claude Code instructions for MetaMask/metamask-mobile, a project described as: Mobile web browser providing access to websites that use the Ethereum blockchain.
full-page-pdf-snap AGENTS.md
Instructions for Bubu89/full-page-pdf-snap, covering agents.md, worum es geht, wo du stehst, vor der ersten änderung and die regeln, die hier anders sind als üblich.