security-ai-keys

To scan your codebase for exposed AI API keys, run this Skill in your project directory. It uses ripgrep to efficiently pattern-match across files, identifying leaked keys for providers like OpenAI, Anthropic, and Gemini in environment variables, client-side code, build artifacts, and logs.

Leaked OpenAI or Anthropic API keys often appear in environment variables, client-side code, build artifacts, or logs. This Skill detects these common leakage patterns by scanning project files for specific string formats associated with major AI providers.

Yes, you need ripgrep installed to audit your project for AI key leakage. This Skill depends on ripgrep to perform efficient pattern matching and quickly scan across all your project files for exposed API keys.

The best way to prevent API key leakage when integrating AI providers is to proactively scan your project before deployment. This Skill identifies exposed keys and provides a hardening checklist recommending redaction strategies and best practices for secret management.

Yes, this tool can detect API keys exposed in build artifacts and logs. It specifically pinpoints these leakage paths along with environment variables and client-side code when scanning your codebase for exposed AI provider credentials.