skills.rest
LuminairPrime
LuminairPrimeCOMMUNITY
Explore all skills by this author →
GitHub

secret-scanner

Detect API keys, credentials, and tokens in code during file changes and commits.

1|Updated Mar 9, 2026
Search Tags:#security#secrets#credentials#environment-variables#api-keys#code-scanning
One-click install
npx skills add https://github.com/LuminairPrime/openwrt-docs4ai-pipeline --skill secret-scanner-luminairprime
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: secret-scanner
Source: https://github.com/LuminairPrime/openwrt-docs4ai-pipeline/tree/main/.claude/skills/secret-scanner
Command: npx skills add https://github.com/LuminairPrime/openwrt-docs4ai-pipeline --skill secret-scanner-luminairprime

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Exposed secrets, credentials, and tokens in codebases can lead to security breaches and compliance risk; this skill detects and prevents such leaks before they impact systems.

Core Features & Use Cases

  • Pre-commit and change scanning: Detects API keys, credentials, and tokens in code, config files, and environment variables during development and deployment.
  • Alerts and guidance: Provides actionable alerts and quick fixes to move secrets to secure storage or environment variables.
  • Usage scenarios: Ideal for CI pipelines, code reviews, and local development to prevent secret exposure.

Quick Start

Run a scan across your project to identify exposed secrets and apply recommended fixes.

Frequently Asked Questions about secret-scanner

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

FAQPage Schema
How do I scan code for exposed API keys and credentials before committing?▼

Scanning code for exposed API keys and credentials before committing involves detecting secrets during file changes and security events. This process identifies insecure patterns and applies quick fixes to move tokens to secure storage.

What is secret scanning in CI pipelines and how does it prevent leaks?▼

Secret scanning in CI pipelines is the automated detection of credentials and tokens in code during deployment. It prevents leaks by enforcing detection patterns, alerting developers, and guiding remediation to block insecure practices across environments.

How do I detect environment variables and tokens in my codebase config files?▼

Detecting environment variables and tokens in codebase config files requires scanning during local development and code reviews. The detection mechanism identifies exposed secrets and provides actionable alerts to move credentials to secure environment variables.

Can I use automated secret detection for local development and code reviews?▼

You can use automated secret detection for local development and code reviews. It is designed to scan file changes as they happen, alerting you to exposed credentials and guiding remediation before secrets impact production systems.

What is the best way to remediate exposed secrets and tokens in code?▼

The best way to remediate exposed secrets and tokens in code is to use automated detection that provides actionable alerts and quick fixes. This guides you to move credentials to secure storage or environment variables, blocking insecure practices.

Related Skills

Explore More Software Engineering Skills→
UseAI-proUseAI-pro
70

credential-scanner

Scan project workspaces for exposed credentials, API keys, and secrets.

Official
Intermediate
L3DigitalNetL3DigitalNet
6

keepass-credential-anthropic

Store, retrieve, and rotate Anthropic API credentials in a protected vault.

Official
Advanced
Rune-kitRune-kit
82

sentinel

Scan code commits for secrets, OWASP top 10 patterns, and dependency vulnerabilities.

Official
Advanced
diegoknskdiegoknsk

security

Configures JWT authentication, secret handling, rate limiting for APIs.

Community
Advanced