no-more-leaked-keys 1.0.0

package/LICENSE

@@ -0,0 +1,63 @@
+No More Leaked Keys - License
+
+Copyright (c) 2026 Andrew Naegele. All Rights Reserved.
+
+================================================================================
+GRANT OF LICENSE
+================================================================================
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to use,
+copy, modify, and distribute the Software for personal and commercial purposes,
+subject to the following conditions:
+
+================================================================================
+CONDITIONS
+================================================================================
+
+1. ATTRIBUTION REQUIRED
+   You must give appropriate credit to Andrew Naegele, provide a link to the
+   original repository, and indicate if changes were made. You may do so in
+   any reasonable manner, but not in any way that suggests the author endorses
+   you or your use.
+
+2. NOT FOR RESALE
+   You may NOT sell, sublicense, or otherwise commercialize the Software itself.
+   You MAY use the Software as part of a larger commercial project or service,
+   but the Software itself cannot be the product being sold.
+
+3. NO WARRANTY
+   THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+   IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+   FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+   AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+   LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+   SOFTWARE.
+
+4. SHARE IMPROVEMENTS
+   If you improve this Software, consider contributing back to the community
+   by submitting a pull request to the original repository.
+
+================================================================================
+SUPPORT THE CREATOR
+================================================================================
+
+If this Software helped you, consider:
+
+  - Starring the GitHub repository
+  - Following Andrew Naegele on social media
+  - Joining the Vibe Marketing community
+
+CONNECT:
+
+  Community:  https://skool.com/vibe-marketing
+  Website:    https://callvaultai.com
+  X/Twitter:  https://x.com/andrewnaegele
+  LinkedIn:   https://linkedin.com/in/andrewnaegele
+  Instagram:  https://instagram.com/andrew.naegele
+  Facebook:   https://facebook.com/andrewnaegele
+
+================================================================================
+
+Copyright (c) 2026 Andrew Naegele. All Rights Reserved.

package/README.md

@@ -0,0 +1,395 @@
+# No More Leaked Keys
+
+**Stop accidentally committing API keys to git.** Store them in macOS Keychain, populate `.env` files on demand.
+
+[![License](https://img.shields.io/badge/license-Custom-blue.svg)](#license)
+[![macOS](https://img.shields.io/badge/platform-macOS-lightgrey.svg)](#requirements)
+[![Claude Code](https://img.shields.io/badge/Claude%20Code-Skill-purple.svg)](#installation)
+
+---
+
+## The Problem (You've Been Here)
+
+You're building an app. You need API keys. So you do what everyone does:
+
+```bash
+# .env file
+OPENAI_API_KEY=sk-abc123...
+STRIPE_SECRET_KEY=sk_live_...
+DATABASE_URL=postgres://user:password@...
+```
+
+Then one day:
+
+- You forget `.env` isn't in `.gitignore`
+- You `git add .` and push
+- **Your keys are now public**
+- Bots scrape GitHub constantly — they find your key in minutes
+- You wake up to a $10,000 AWS bill
+- Or your OpenAI account is drained
+- Or your database is wiped
+
+**This happens every single day to developers.**
+
+Even if you're careful:
+- Keys are visible when you paste them
+- Keys sit in your clipboard (easy to accidentally paste in Slack)
+- Keys are stored in plain text files
+- Screen sharing? Recording? Your keys are exposed.
+
+---
+
+## The Solution
+
+**Store API keys in macOS Keychain. Never in files.**
+
+- Keychain is **encrypted** (AES-256)
+- Keychain is **local** (not synced to cloud)
+- Keychain is **scriptable** (we can automate it)
+- Generate `.env` files **on demand** from Keychain
+- Keys are **invisible** when you paste them
+- Clipboard is **auto-cleared** after storing
+
+**One Keychain. Every project. Zero risk.**
+
+---
+
+## How It Works
+
+### Step 1: Store Your API Key (One Time)
+
+A Terminal window opens with a secure prompt:
+
+```
+====================================
+  SECURE API KEY INPUT
+====================================
+
+Paste your key below (it will be invisible)
+Then press ENTER
+
+OPENAI_API_KEY: █
+
+[SUCCESS] OPENAI_API_KEY stored in Keychain
+[SUCCESS] Clipboard cleared
+```
+
+**What happens:**
+1. You paste your key — **nothing appears on screen**
+2. Key is encrypted and stored in macOS Keychain
+3. Your clipboard is cleared (can't accidentally paste elsewhere)
+4. The variable is cleared from memory
+
+**You never see the key. It never touches a file. It's encrypted immediately.**
+
+### Step 2: Populate .env (Per Project)
+
+When you start a project that needs environment variables:
+
+```bash
+# The skill reads .env.example and pulls from Keychain
+[OK] OPENAI_API_KEY
+[OK] ANTHROPIC_API_KEY  
+[OK] DATABASE_URL
+[MISSING] STRIPE_KEY  # Not in Keychain yet - prompts to add
+
+Done. .env created with secure permissions (600).
+```
+
+The `.env` file is:
+- Created with **owner-only permissions** (`chmod 600`)
+- Automatically added to **`.gitignore`**
+- **Never committed to git**
+
+### Step 3: Use In Your Code (Normal .env Usage)
+
+Your code works exactly the same:
+
+**Python:**
+```python
+from dotenv import load_dotenv
+import os
+
+load_dotenv()
+api_key = os.environ['OPENAI_API_KEY']
+```
+
+**Node.js:**
+```javascript
+require('dotenv').config()
+const apiKey = process.env.OPENAI_API_KEY
+```
+
+**The difference:** Your keys came from Keychain, not a file you might accidentally commit.
+
+---
+
+## Security Model
+
+Every layer is protected:
+
+| Attack Vector | Protection |
+|---------------|-----------|
+| **Visible on screen** | `read -s` — silent input, nothing displayed |
+| **Stays in memory** | `unset` — variable cleared immediately |
+| **Left in clipboard** | `pbcopy < /dev/null` — clipboard auto-cleared |
+| **Stored in plain text** | macOS Keychain — AES-256 encryption |
+| **Readable by others** | `chmod 600` — owner-only file permissions |
+| **Committed to git** | Auto-adds `.env` to `.gitignore` |
+| **In terminal history** | Key never part of a command string |
+| **MCP server config** | Direct file edit — never echoed to terminal |
+
+---
+
+## Adding MCP Servers Securely
+
+**WARNING: Anthropic's `claude mcp add` command exposes your API key!**
+
+The native `claude mcp add` command has a security flaw - it **echoes your API key** to the terminal:
+
+```bash
+# DANGEROUS - This prints your key to the terminal!
+claude mcp add --transport http tally https://api.tally.so/mcp \
+  --header "Authorization: Bearer $TALLY_API_KEY"
+# Output includes: "Authorization": "Bearer sk-actual-key-here"  <-- EXPOSED!
+```
+
+**This skill fixes that.** After installation:
+1. The unsafe command is **automatically blocked** by a security hook
+2. You use `/secrets` or `/add-mcp` instead
+3. Keys are pulled from Keychain silently and written directly to config
+4. Keys are **never echoed anywhere**
+
+```
+> /secrets
+> "Add MCP server securely"
+> MCP name: tally
+> MCP URL: https://api.tally.so/mcp
+> Key name in Keychain: TALLY_API_KEY
+> Target: claude
+
+[SUCCESS] Added tally MCP to Claude Code
+[SUCCESS] Key retrieved from Keychain (never displayed)
+```
+
+---
+
+## Installation
+
+### NPM Install (Recommended)
+
+```bash
+npx no-more-leaked-keys
+```
+
+Or install globally:
+
+```bash
+npm install -g no-more-leaked-keys
+```
+
+### Alternative: Git Clone
+
+```bash
+git clone https://github.com/Vibe-Marketer/no-more-leaked-keys.git && cd no-more-leaked-keys && ./install.sh
+```
+
+This installs:
+- The skill (`/secrets`)
+- The commands (`/add-mcp`)
+- **A security hook that blocks unsafe `claude mcp add` commands**
+
+Then restart Claude Code.
+
+### What the Security Hook Does
+
+After installation, if anyone (you or Claude) tries to run `claude mcp add` with authentication headers, it gets **automatically blocked**:
+
+```
+BLOCKED: claude mcp add with auth headers exposes your API key in terminal output!
+
+Use /secrets or /add-mcp instead - these pull keys from Keychain securely 
+without exposing them.
+```
+
+This protects you even if you forget and try to use the unsafe command.
+
+### Manual Installation
+
+If you prefer to install manually:
+
+```bash
+git clone https://github.com/Vibe-Marketer/no-more-leaked-keys.git
+cd no-more-leaked-keys
+
+# Install skill and commands
+mkdir -p ~/.claude/skills ~/.claude/commands ~/.claude/hooks
+cp -r keychain-secrets ~/.claude/skills/
+cp commands/*.md ~/.claude/commands/
+cp hooks/*.sh ~/.claude/hooks/
+chmod +x ~/.claude/hooks/*.sh
+
+# Then manually add the hook to ~/.claude/settings.json (see install.sh for details)
+```
+
+**Usage:**
+- Type `/secrets` in Claude Code
+- Or just say "add my API key" or "set up .env"
+
+### For Everyone (Manual Terminal Usage)
+
+You don't need Claude Code. Use these commands directly:
+
+**Add a key to Keychain:**
+```bash
+echo -n "Paste API key: " && read -s K && \
+security add-generic-password -a "$USER" -s "OPENAI_API_KEY" -w "$K" && \
+unset K && pbcopy < /dev/null && echo -e "\nStored!"
+```
+
+**Retrieve a key:**
+```bash
+security find-generic-password -a "$USER" -s "OPENAI_API_KEY" -w
+```
+
+**Generate .env from Keychain:**
+```bash
+echo "OPENAI_API_KEY=$(security find-generic-password -a "$USER" -s "OPENAI_API_KEY" -w)" > .env
+chmod 600 .env
+echo ".env" >> .gitignore
+```
+
+---
+
+## Why Keychain Over Other Methods?
+
+| Method | Problem |
+|--------|---------|
+| **`.env` files** | Can be committed to git, stored in plain text |
+| **Shell config (`~/.zshrc`)** | Visible in dotfiles, often synced to cloud |
+| **Password managers (1Password, etc.)** | Requires manual copy/paste every time |
+| **Environment variables in CI/CD** | Great for prod, but doesn't help local dev |
+| **macOS Keychain** | Encrypted, local, scriptable, automatic |
+
+---
+
+## FAQ
+
+### Is this actually secure?
+
+Yes. macOS Keychain uses AES-256 encryption, the same standard used by banks and governments. Your keys are encrypted at rest and protected by your macOS login password.
+
+### What if someone has access to my Mac?
+
+If someone has your Mac AND your login password, they can access your Keychain. But at that point, they can also access everything else. Keychain is as secure as your Mac login.
+
+### Does this work with Touch ID / Face ID?
+
+Yes. Keychain integrates with biometric authentication. You may be prompted the first time an app accesses a key.
+
+### Can I use this on Linux or Windows?
+
+Not directly — this uses macOS Keychain. However:
+- **Linux:** You could adapt this to use `gnome-keyring` or `pass`
+- **Windows:** You could use Windows Credential Manager
+
+PRs welcome for cross-platform support!
+
+### What happens if I need to share keys with my team?
+
+This is for **local development security**. For team/production secrets, use:
+- 1Password / Bitwarden shared vaults
+- AWS Secrets Manager
+- HashiCorp Vault
+- Doppler
+
+### Will this slow down my workflow?
+
+No. You add each key once. After that, populating `.env` for any project takes seconds.
+
+### What if I delete a key by accident?
+
+It's gone. Keychain doesn't have a recycle bin. You'll need to get the key again from wherever you originally got it (OpenAI dashboard, Stripe dashboard, etc.).
+
+### Does the `.env` file contain my actual keys?
+
+Yes, temporarily. The `.env` file is created with your keys so your code can read them. But:
+- It has `600` permissions (only you can read it)
+- It's in `.gitignore` (never committed)
+- You can delete it and regenerate anytime
+
+The difference is: you're not manually pasting keys where you might accidentally commit them.
+
+---
+
+## File Structure
+
+```
+no-more-leaked-keys/
+├── README.md                 # You're reading this
+├── LICENSE                   # Usage terms
+├── install.sh                # One-command installer
+├── keychain-secrets/         # Claude Code skill
+│   ├── SKILL.md
+│   ├── workflows/
+│   │   ├── add-key.md        # Store keys in Keychain
+│   │   ├── add-mcp.md        # Securely add MCP servers
+│   │   ├── list-keys.md
+│   │   ├── populate-env.md
+│   │   └── remove-key.md
+│   └── references/
+│       ├── keychain-commands.md
+│       └── env-file-patterns.md
+├── commands/
+│   ├── secrets.md            # /secrets slash command
+│   └── add-mcp.md            # /add-mcp slash command
+├── hooks/
+│   └── block-unsafe-mcp-add.sh  # Security hook (blocks unsafe commands)
+└── test-project/             # Example project for testing
+    ├── .env.example
+    ├── test-node.js
+    └── test-python.py
+```
+
+---
+
+## Requirements
+
+- **macOS** (uses Keychain and `security` CLI)
+- **Claude Code** (optional, for the skill — or use manual commands)
+
+---
+
+## Contributing
+
+PRs welcome! Please ensure no actual secrets are committed (obviously).
+
+---
+
+## Connect
+
+Built by **Andrew Naegele**
+
+- **Community:** [skool.com/vibe-marketing](https://skool.com/vibe-marketing)
+- **Website:** [callvaultai.com](https://callvaultai.com)
+- **X/Twitter:** [@andrewnaegele](https://x.com/andrewnaegele)
+- **LinkedIn:** [linkedin.com/in/andrewnaegele](https://linkedin.com/in/andrewnaegele)
+- **Instagram:** [@andrew.naegele](https://instagram.com/andrew.naegele)
+- **Facebook:** [facebook.com/andrewnaegele](https://facebook.com/andrewnaegele)
+
+---
+
+## License
+
+See [LICENSE](LICENSE) for full terms.
+
+**TL;DR:** Free to use for personal and commercial projects. Not for resale. Give credit. Star the repo.
+
+---
+
+**Stop leaking keys. Start using Keychain.**
+
+If this saved you from a $10,000 mistake, consider:
+- Starring this repo
+- Joining the community at [skool.com/vibe-marketing](https://skool.com/vibe-marketing)
+- Sharing with a developer friend who needs this

package/bin/install.js

@@ -0,0 +1,216 @@
+#!/usr/bin/env node
+
+const fs = require('fs');
+const path = require('path');
+const os = require('os');
+const { execSync } = require('child_process');
+
+// Colors for terminal output
+const colors = {
+  reset: '\x1b[0m',
+  bright: '\x1b[1m',
+  green: '\x1b[32m',
+  yellow: '\x1b[33m',
+  red: '\x1b[31m',
+  cyan: '\x1b[36m'
+};
+
+function log(message, color = 'reset') {
+  console.log(`${colors[color]}${message}${colors.reset}`);
+}
+
+function logStep(step, total, message) {
+  log(`[${step}/${total}] ${message}`, 'cyan');
+}
+
+function logSuccess(message) {
+  log(`  ✓ ${message}`, 'green');
+}
+
+function logWarning(message) {
+  log(`  ⚠ ${message}`, 'yellow');
+}
+
+function logError(message) {
+  log(`  ✗ ${message}`, 'red');
+}
+
+// Check if running on macOS
+if (os.platform() !== 'darwin') {
+  log('\n============================================', 'red');
+  log('  This tool only works on macOS', 'red');
+  log('============================================', 'red');
+  log('\nIt uses macOS Keychain for secure key storage.');
+  log('For other platforms, see the README for alternatives.\n');
+  process.exit(1);
+}
+
+const HOME = os.homedir();
+const PACKAGE_DIR = path.join(__dirname, '..');
+
+// Directories
+const CLAUDE_DIR = path.join(HOME, '.claude');
+const SKILLS_DIR = path.join(CLAUDE_DIR, 'skills');
+const COMMANDS_DIR = path.join(CLAUDE_DIR, 'commands');
+const HOOKS_DIR = path.join(CLAUDE_DIR, 'hooks');
+const SETTINGS_FILE = path.join(CLAUDE_DIR, 'settings.json');
+
+log('\n======================================', 'bright');
+log('  No More Leaked Keys - Installer', 'bright');
+log('======================================\n', 'bright');
+
+const TOTAL_STEPS = 6;
+
+// Step 1: Create directories
+logStep(1, TOTAL_STEPS, 'Creating directories...');
+[SKILLS_DIR, COMMANDS_DIR, HOOKS_DIR].forEach(dir => {
+  if (!fs.existsSync(dir)) {
+    fs.mkdirSync(dir, { recursive: true });
+  }
+});
+logSuccess('Directories ready');
+
+// Step 2: Install skill
+logStep(2, TOTAL_STEPS, 'Installing keychain-secrets skill...');
+const skillSrc = path.join(PACKAGE_DIR, 'keychain-secrets');
+const skillDest = path.join(SKILLS_DIR, 'keychain-secrets');
+fs.cpSync(skillSrc, skillDest, { recursive: true });
+logSuccess('Skill installed');
+
+// Step 3: Install commands
+logStep(3, TOTAL_STEPS, 'Installing slash commands...');
+const commandsSrc = path.join(PACKAGE_DIR, 'commands');
+fs.readdirSync(commandsSrc).forEach(file => {
+  if (file.endsWith('.md')) {
+    fs.copyFileSync(
+      path.join(commandsSrc, file),
+      path.join(COMMANDS_DIR, file)
+    );
+  }
+});
+logSuccess('Commands installed: /secrets, /add-mcp');
+
+// Step 4: Install hook
+logStep(4, TOTAL_STEPS, 'Installing security hook...');
+const hookSrc = path.join(PACKAGE_DIR, 'hooks', 'block-unsafe-mcp-add.sh');
+const hookDest = path.join(HOOKS_DIR, 'block-unsafe-mcp-add.sh');
+fs.copyFileSync(hookSrc, hookDest);
+fs.chmodSync(hookDest, '755');
+logSuccess('Security hook installed');
+
+// Step 5: Configure Claude Code settings
+logStep(5, TOTAL_STEPS, 'Configuring Claude Code...');
+
+let settings = {};
+if (fs.existsSync(SETTINGS_FILE)) {
+  try {
+    settings = JSON.parse(fs.readFileSync(SETTINGS_FILE, 'utf8'));
+  } catch (e) {
+    logWarning('Could not parse existing settings.json, creating new one');
+  }
+}
+
+if (!settings.hooks) settings.hooks = {};
+if (!settings.hooks.PreToolUse) settings.hooks.PreToolUse = [];
+
+// Check if hook already exists
+const hookExists = settings.hooks.PreToolUse.some(
+  hook => JSON.stringify(hook).includes('block-unsafe-mcp-add.sh')
+);
+
+if (!hookExists) {
+  settings.hooks.PreToolUse.push({
+    matcher: 'Bash',
+    hooks: [{
+      type: 'command',
+      command: 'bash ~/.claude/hooks/block-unsafe-mcp-add.sh'
+    }]
+  });
+  fs.writeFileSync(SETTINGS_FILE, JSON.stringify(settings, null, 2));
+  logSuccess('Claude Code hook configured');
+} else {
+  logSuccess('Claude Code hook already configured');
+}
+
+// Step 6: Add shell protection
+logStep(6, TOTAL_STEPS, 'Adding shell-level protection...');
+
+const shellProtection = `
+# ============================================
+# No More Leaked Keys - Security Protection
+# Blocks unsafe "claude mcp add" with auth headers
+# ============================================
+claude() {
+    if [[ "$1" == "mcp" && "$2" == "add" ]]; then
+        for arg in "$@"; do
+            if [[ "$arg" =~ [Aa]uthorization.*[Bb]earer || "$arg" =~ [Bb]earer ]]; then
+                echo ""
+                echo "============================================"
+                echo "  BLOCKED: Unsafe MCP Command Detected"
+                echo "============================================"
+                echo ""
+                echo 'The "claude mcp add" command with auth headers'
+                echo "exposes your API key in terminal output!"
+                echo ""
+                echo "Use these safe alternatives instead:"
+                echo "  - /secrets  (in Claude Code)"
+                echo "  - /add-mcp  (in Claude Code)"
+                echo ""
+                echo "These pull keys from Keychain securely."
+                echo "See: https://github.com/Vibe-Marketer/no-more-leaked-keys"
+                echo ""
+                return 1
+            fi
+        done
+    fi
+    command claude "$@"
+}
+`;
+
+// Detect shell config
+let shellRc = path.join(HOME, '.zshrc');
+if (!fs.existsSync(shellRc)) {
+  shellRc = path.join(HOME, '.bashrc');
+}
+
+let shellContent = '';
+if (fs.existsSync(shellRc)) {
+  shellContent = fs.readFileSync(shellRc, 'utf8');
+}
+
+if (!shellContent.includes('No More Leaked Keys - Security Protection')) {
+  fs.appendFileSync(shellRc, shellProtection);
+  logSuccess(`Shell protection added to ${shellRc}`);
+} else {
+  logSuccess('Shell protection already configured');
+}
+
+// Done!
+log('\n======================================', 'green');
+log('  Installation Complete!', 'green');
+log('======================================\n', 'green');
+
+log("What's installed:", 'bright');
+log('  • Skill: ~/.claude/skills/keychain-secrets/');
+log('  • Commands: /secrets, /add-mcp');
+log('  • Claude Code hook: Blocks unsafe commands from Claude');
+log('  • Shell protection: Blocks unsafe commands from terminal');
+
+log('\nUsage:', 'bright');
+log('  • Type /secrets to manage API keys');
+log('  • Type /add-mcp to securely add MCP servers');
+
+log('\nProtection is now active at TWO levels:', 'bright');
+log('  1. Claude Code hook - blocks Claude from running unsafe commands');
+log('  2. Shell function - blocks YOU from running unsafe commands');
+
+log('\nTo activate shell protection now, run:', 'yellow');
+log(`  source ${shellRc}\n`);
+
+log('Or restart your terminal.\n');
+
+// Social links
+log('─────────────────────────────────────', 'cyan');
+log('Built by Andrew Naegele', 'cyan');
+log('Community: https://skool.com/vibe-marketing', 'cyan');
+log('─────────────────────────────────────\n', 'cyan');

package/commands/add-mcp.md

@@ -0,0 +1,17 @@
+---
+description: Securely add an MCP server without exposing API keys
+allowed-tools: ["Skill", "Bash", "Read", "Write", "Edit"]
+---
+
+Invoke the keychain-secrets skill to securely add an MCP server.
+
+**NEVER use `claude mcp add` with authentication headers - it exposes keys in terminal output!**
+
+This command will:
+1. Verify the API key exists in Keychain
+2. Add the MCP config by directly editing the config file
+3. Never echo or display the key
+
+Arguments: $ARGUMENTS
+
+Use workflow: add-mcp.md

package/commands/secrets.md

@@ -0,0 +1,12 @@
+---
+description: Manage API keys securely with macOS Keychain
+allowed-tools: ["Skill"]
+---
+
+Invoke the keychain-secrets skill for: $ARGUMENTS
+
+Use the keychain-secrets skill to help with API key management. This skill provides secure workflows for:
+- Populating .env files from Keychain
+- Adding new API keys securely (keys never visible on screen)
+- Listing available keys
+- Removing keys from Keychain