secrets-scan

Name: secrets-scan
Availability: InStock
Author: ss2608-dev

Scan code repositories for committed secrets, API keys, and credentials.

Updated Aug 23, 2026

Search Tags:#devops #security #secrets #credentials #api keys #code scan

Ready to run

npx skills add https://github.com/SS2608-dev/Resilience --skill secrets-scan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: secrets-scan
Source: https://github.com/SS2608-dev/Resilience/tree/main/.claude/skills/security/secrets-scan
Command: npx skills add https://github.com/SS2608-dev/Resilience --skill secrets-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill prevents accidental exposure of sensitive information like API keys, passwords, and credentials by scanning your codebase for them before they are committed.

Core Features & Use Cases

Secret Detection: Identifies various types of secrets including API keys, tokens, passwords, and cloud provider credentials using regular expressions.
Targeted Scanning: Scans specified file types while excluding common directories like node_modules and .next.
Use Case: Before pushing your code changes, run this skill to ensure no hardcoded database passwords or API keys are present, preventing potential security breaches.

Quick Start

Run a secrets scan on the current directory, checking all TypeScript and environment files.

Frequently Asked Questions about secrets-scan

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

FAQPage Schema

How do I scan my code repository for accidentally committed API keys and credentials?▼

To scan your code repository for committed API keys and credentials, this Skill uses pattern matching and known key formats to identify and flag sensitive data leakage across source code, configuration files, and shell scripts.

Does secrets scanning exclude build artifacts and dependency directories?▼

Yes, secrets scanning excludes common build artifacts and version control directories like node_modules and .next, targeting only relevant source code and configuration files to prevent false positives during the secret detection process.

How do I check for hardcoded database passwords and tokens before pushing code changes?▼

To check for hardcoded database passwords and tokens before pushing, run a scan on your current directory to identify various secrets using regular expressions, enforcing security best practices by flagging sensitive data leakage.

What types of secrets and credentials can a code scanner detect?▼

A code scanner detects various types of secrets including API keys, tokens, passwords, and cloud provider credentials by applying regular expressions and known key formats to your codebase files.

Can I scan specific file types like TypeScript and environment files for sensitive data?▼

Yes, you can scan specific file types like TypeScript and environment files for sensitive data, running targeted checks on specified extensions while automatically ignoring common directories to streamline the secret detection workflow.