How to let AI code with your real API keys (without leaking them)

You want Claude to integrate Stripe. You want Cursor to build your OpenAI pipeline. But your API keys are in .env, and AI can read them. GitGuardian found 39.6 million secrets leaked on GitHub in 2025. AI-assisted commits leak at 2x the baseline rate. Phantom fixes this in one command. The Problem When you use AI coding tools, your .env secrets enter the LLM context window: Claude Code reads .env to understand your project Cursor indexes your workspace files Copilot suggests code containing your keys Those keys can leak via session logs, prompt injection, or training data. The Solution: Phantom Tokens $ npx phantom-secrets init One command: Reads your .env and detects real secrets Stores them in your OS keychain (encrypted) Rewrites .env with worthless phantom tokens Auto-configures Claude Code MCP server Your .env now looks like: OPENAI_API_KEY = phm_a7f3b9e2c1d4f6a8 ... STRIPE_SECRET_KEY = phm_2ccb5a1e9f8d7b3c ... These tokens are worthless. Safe to leak. Safe for AI to read. How It