brewcode:secrets-scan

Scan git-tracked files for hardcoded secrets and credentials.

30|2|Updated Jan 24, 2026

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

Ready to run

npx skills add https://github.com/kochetkov-ma/claude-brewcode --skill brewcode-secrets-scan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brewcode:secrets-scan
Source: https://github.com/kochetkov-ma/claude-brewcode/tree/main/brewcode/skills/secrets-scan
Command: npx skills add https://github.com/kochetkov-ma/claude-brewcode --skill brewcode-secrets-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automatically scans your codebase for hardcoded secrets like passwords, API keys, and tokens, preventing accidental exposure and security breaches.

Core Features & Use Cases

Comprehensive Secret Detection: Identifies a wide range of sensitive information using predefined patterns.
Automated Scanning: Integrates seamlessly into development workflows to scan git-tracked files.
Remediation Options: Offers interactive fixes for detected secrets, including deletion, moving to environment variables, or adding to .gitignore.
Use Case: Before committing code, run this skill to ensure no API keys or database credentials are accidentally included, safeguarding your project's security.

Quick Start

Run /secrets-scan to scan for secrets and generate a report.

Frequently Asked Questions about brewcode:secrets-scan

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

FAQPage Schema

How do I scan git-tracked files for hardcoded secrets and API keys?▼

You can scan git-tracked files for leaked secrets by running the /secrets-scan command. It uses parallel agents to detect hardcoded credentials like API keys and tokens, generating a detailed report categorized by severity.

How do I remediate leaked credentials found in my codebase?▼

To remediate leaked credentials, the scan provides interactive options for each detected secret. You can delete the sensitive information, move it to environment variables, or add the file to .gitignore directly from the generated report.

Do I need a git repository to run a secrets scan?▼

Yes, executing a secrets scan requires an active git repository context and Bash execution access to list files and set up directories for scanning hardcoded credentials and sensitive information.

What types of sensitive information can a code security audit detect?▼

A secrets scan detects a wide range of hardcoded sensitive information using predefined patterns, including passwords, API keys, tokens, and database credentials accidentally included in your git-tracked files.

When should I run a secrets scan to prevent leaked credentials?▼

Run a secrets scan before committing code to prevent leaked credentials. Integrating this automated scan into your development workflow ensures no sensitive API keys or database credentials are accidentally exposed.