secret-scanning

Detects credential leaks in Git repositories and blocks pushes containing secrets.

Updated Jul 7, 2026

Search Tags:#secret scanning #repository security #credential protection #alert management #push protection

Ready to run

npx skills add https://github.com/voidrot/agents --skill secret-scanning-voidrot

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: secret-scanning
Source: https://github.com/voidrot/agents/tree/main/skills/security/secret-scanning
Command: npx skills add https://github.com/voidrot/agents --skill secret-scanning-voidrot

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures your repository is secure by detecting and addressing potential leaks of credentials, such as API keys or personal access tokens.

Core Features & Use Cases

Secret Detection: Scans the repository for leaked credentials across all branches and files.
Push Protection: Blocks pushes containing detected secrets, preventing them from reaching the repository.
Custom Patterns: Allows the definition of custom secret patterns for organization-specific needs.
Alert Management: Manages and resolves alerts related to detected secrets, including triage and remediation workflows.

Quick Start

Enable the secret-scanning skill in your repository and follow the guided steps to configure and activate secret scanning.

Frequently Asked Questions about secret-scanning

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

FAQPage Schema

How does push protection prevent leaked credentials from entering a Git repository?▼

Push protection blocks pushes containing detected secrets, preventing credentials like API keys from reaching your Git repository. It scans content before acceptance and triggers alerts for immediate remediation.

What is the process for configuring custom secret scanning patterns?▼

Configuring custom secret scanning patterns allows defining organization-specific rules to detect unique credentials. This ensures specialized secrets are caught during repository scans alongside standard API keys.

How do I manage and resolve alerts for detected secrets in my repository?▼

Alert management handles detected secrets by triaging notifications and prioritizing credential rotation. It guides remediation workflows to resolve security vulnerabilities across all repository branches.

Does secret scanning check all branches and files for leaked API keys?▼

Yes, secret scanning detects leaked API keys and tokens across all branches and files. It performs comprehensive repository-level scans to identify and address credential leaks.

What is the best way to secure a repository against credential leaks?▼

The best way to secure a repository is combining secret scanning with push protection enforcement. This scans all files while blocking pushes containing credentials, supported by custom pattern configuration and alert management.