security-ai-keys

Detect and mitigate AI API key leakage across application environments.

7|2|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/justinlevinedotme/jalco-opencode --skill security-ai-keys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-ai-keys
Source: https://github.com/justinlevinedotme/jalco-opencode/tree/main/opencode/.config/opencode/skills/security-ai-keys
Command: npx skills add https://github.com/justinlevinedotme/jalco-opencode --skill security-ai-keys

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires rg, and includes scripts (resource) components.

What problem does it solve?

This Skill helps identify and mitigate AI API key leakage and insecure secret handling in applications and codebases, reducing risk from exposed credentials.

Core Features & Use Cases

  • Secret detection: scans for common leakage paths (client-side env vars, build artifacts, logs) and flags risky configurations.
  • Redaction guidance: provides actionable steps to redact keys in logs, outputs, and telemetry.
  • Audit-ready: generates a checklist aligned with devsecops practices to rotate keys and enforce server-side usage.
  • Use Case: Imagine a web app that accidentally ships a NEXT_PUBLIC_AI_KEY in the browser; this skill guides you to relocate keys to server-side storage and rotate them.

Quick Start

Run the AI key leakage scan against your codebase to locate exposed keys and verify redaction practices.

Frequently Asked Questions about security-ai-keys

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan my codebase for exposed AI API keys?

AI API key leakage happens when secrets are exposed in client-side environment variables, build artifacts, or insecure logs. Scanning your codebase flags these risky configurations and helps mitigate accidental credential exposure across your application environments.

How do I redact AI keys from application logs and telemetry?

You can detect insecure secret handling in CI pipelines and containers by applying a secret hygiene scan across those environments. It locates exposed keys, verifies redaction practices, and enforces server-side secret usage to ensure audit-ready configurations.

How do I enforce server-side usage for leaked NEXT_PUBLIC AI keys?

To scan for exposed AI API keys, run a secret detection scan against your codebase. This identifies common leakage paths like client-side environment variables, build artifacts, and insecure logs, providing actionable redaction and rotation steps.

Can I use ripgrep to perform a security audit for AI key leaks?

AI API key leakage happens when secrets are exposed in client-side environment variables, build artifacts, or insecure logs. Scanning your codebase flags these risky configurations and helps mitigate accidental credential exposure across your application environments.

What is the best way to rotate exposed AI API keys in a web app?

You can detect insecure secret handling in CI pipelines and containers by applying a secret hygiene scan across those environments. It locates exposed keys, verifies redaction practices, and enforces server-side secret usage to ensure audit-ready configurations.