Agent skill · security · aiskillstore
secrets-gitleaks
Hardcoded secret detection and prevention in git repositories and codebases using Gitleaks. Identifies passwords, API keys, tokens, and credentials through regex-based pattern matching and entropy analysis. Use when: (1) Scanning repositories for exposed secrets and credentials, (2) Implementing pre-commit hooks to prevent secret leakage, (3) Integrating secret detection into CI/CD pipelines, (4) Auditing codebases for compliance violations (PCI-DSS, SOC2, GDPR), (5) Establishing baseline secret detection and tracking new exposures, (6) Remediating historical secret exposures in git history.
Why this skill is useful
Adds executable scripts for integrating Gitleaks into CI/CD pipelines and pre-commit hooks, which are not commonly found in public documentation.
What it needs
Requires git, gitleaks installed locally. About 8k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Secrets Detection with Gitleaks Overview Gitleaks is a secret detection tool that scans git repositories, files, and directories for hardcoded credentials including passwords, API keys, tokens, and other sensitive information. It uses regex-based pattern matching combined with Shannon entropy analysis to identify secrets that could lead to unauthorized access if exposed. This skill provides comprehensive guidance for integrating Gitleaks into DevSecOps workflows, from pre-commit hooks to CI/CD pipelines, with emphasis on preventing secret leakage before code reaches production. Quick Start Scan current repository for secrets: Core Workflows 1. Repository Scanning Scan existing repositories to identify exposed secrets: When to use: Initial security audit, compliance checks, incident response. 2. Pre-Commit Hook Protection Prevent secrets from being committed in the first place: Use the bundled script for automated hook installation: When to use: Developer workstation setup, team onboarding, mandatory security controls. 3. CI/CD Pipeline Integration GitHub Actions GitLab CI When to use: Automated security gates, pull request checks, release validation. 4. Baseline and Incremental Scanning Establish security baseline and track only new secrets: When to use: Legacy codebase remediation, phased rollout, compliance tracking. 5. Configuration Customization Create custom .gitleaks.toml configuration: Use bundled configuration templates in assets/: assets/config-strict.toml - Strict detection (low false negatives) assets/config-balanced.toml - Balanced detection (recommended) assets/config-custom.toml - Template for custom rules When to use: Reducing false positives, adding proprietary secret patterns, organizational standards. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/secrets-gitleaks