Individual skill
implementing-secret-scanning-with-gitleaks
This skill covers implementing Gitleaks for detecting and preventing hardcoded secrets in git repositories. It addresses configuring pre-commit hooks, CI/CD pipeline integration, custom rule authoring for organization-specific secrets, baseline management for existing repositories, and remediation workflows for exposed credentials.
skills/implementing-secret-scanning-with-gitleaks/SKILL.md
Source commit 54a798831d2266a3ca61ce68a7acb80b81160d57
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 35,913
- Repository last updated
- Aug 31, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- claude-code Repository topic
- cybersecurity Repository topic
- incident-response Repository topic
- mitre-attack Repository topic
- penetration-testing Repository topic
- red-team Repository topic
- security Repository topic
- cloud-security Repository topic
- malware-analysis Repository topic
- devsecops Declared skill tag
- cicd Declared skill tag
- secret-scanning Declared skill tag
- gitleaks Declared skill tag
- pre-commit Declared skill tag
- secure-sdlc Declared skill tag
- devops Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
LICENSEasset · 11,255 bytesSKILL.mdcore · 11,337 bytesSKILL.mdcore · 11,337 bytesSKILL.mdcore · 11,337 bytesSKILL.mdcore · 11,337 bytesSKILL.mdcore · 11,337 bytesSKILL.mdcore · 11,337 bytesSKILL.mdcore · 11,337 bytesSKILL.mdcore · 11,337 bytesSKILL.mdcore · 11,337 bytesSKILL.mdcore · 11,337 bytesSKILL.mdcore · 11,337 bytesSKILL.mdcore · 11,337 bytesSKILL.mdcore · 11,337 bytesSKILL.mdcore · 11,337 bytesSKILL.mdcore · 11,337 bytesassets/template.mddoc · 4,781 bytesreferences/api-reference.mddoc · 4,621 bytesreferences/standards.mddoc · 2,298 bytesreferences/workflows.mddoc · 5,114 bytesscripts/agent.pyruns · 7,420 bytesscripts/process.pyruns · 9,999 bytes
Read excerpt
# Implementing Secret Scanning with Gitleaks
## When to Use
- When developers may accidentally commit API keys, passwords, tokens, or private keys to repositories
- When establishing pre-commit gates that prevent secrets from entering the git history
- When scanning existing repository history for previously committed secrets that need rotation
- When compliance requirements mandate secret detection across all source code repositories
- When migrating from manual secret audits to automated continuous scanning
**Do not use** for detecting secrets in running applications or memory (use runtime secret detection), for managing secrets after detection (use Vault or AWS Secrets Manager), or for scanning container images (use Trivy or Grype).
## Prerequisites
