skills.rest
vladkesler
vladkeslerCOMMUNITY
Explore all skills by this author →
GitHub

secret-detection

Scan repositories and configuration files for hardcoded secrets and API keys.

39|6|Updated Feb 9, 2026
Search Tags:#security#secrets#credentials#ripgrep#code-scanning#pattern-matching
One-click install
npx skills add https://github.com/vladkesler/initrunner --skill secret-detection-vladkesler
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: secret-detection
Source: https://github.com/vladkesler/initrunner/tree/main/examples/roles/security-scanner/skills/secret-detection
Command: npx skills add https://github.com/vladkesler/initrunner --skill secret-detection-vladkesler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect hardcoded secrets, API keys, tokens, and credentials embedded in source code to prevent exposure and leakage across repositories and deployments.

Core Features & Use Cases

  • Pattern-based scans across languages and file types to surface secrets in code, configs, and scripts.
  • Integration with repository workflows to run scans on commit or pull request events.
  • Use Case: security teams quickly identify and remediate exposed credentials before they reach production.

Quick Start

Run ripgrep-based scans across your codebase to surface hardcoded secrets.

Frequently Asked Questions about secret-detection

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

FAQPage Schema
How do I detect hardcoded secrets and API keys in source code?▼

Detect hardcoded secrets in source code by running pattern-based scans across your repository to identify exposed API keys, tokens, and credentials in scripts and configuration files.

Can I scan configuration files and multiple programming languages for exposed credentials?▼

Scanning configuration files and multiple programming languages for exposed credentials is fully supported, allowing you to surface embedded tokens across all file types within your branches.

What is the best way to find leaked tokens and credentials before they reach production?▼

The best way to find leaked tokens before production is running ripgrep-based pattern checks across your codebase to flag hardcoded credentials embedded in repository files.

Does this code-scanning tool support configurable ignore patterns for specific files?▼

The code-scanning tool supports configurable ignore patterns, allowing you to exclude specific files and directories from ripgrep checks when detecting hardcoded secrets in your repository.

Why use ripgrep pattern matching for finding secrets in my repository?▼

Ripgrep pattern matching quickly scans repositories and branches to identify hardcoded secrets, producing a concise report of detected matches without requiring complex setup or dependencies.

When should I scan my branches for hardcoded secrets and credentials?▼

Scan your branches for hardcoded secrets and credentials before deployment to prevent exposure, ensuring security teams identify and remediate leaked tokens prior to production releases.

Related Skills

Explore More Software Engineering Skills→
jrmatherlyjrmatherly

error-handling

Standardize API error handling with structured AppError classes and middleware.

Community
Intermediate
igbuendigbuend
8

gitleaks

Detect hardcoded secrets in source code and Git history using Gitleaks.

Community
Intermediate
YokhanYokhan

security-audit

Scan dependencies, code patterns, and configurations to generate structured security audit reports.

Community
Advanced
manastalukdarmanastalukdar
1

secrets-scan

Scan codebases and Git history for exposed secrets using Gitleaks and TruffleHog.

Community
Advanced