skills.rest
AeonDave
AeonDaveCOMMUNITY
Explore all skills by this author →
GitHub

gitleaks

Detect hardcoded secrets and credentials in git repositories and files.

15|1|Updated Feb 12, 2026
Search Tags:#security#secrets#credentials#api keys#gitleaks#code scanning
One-click install
npx skills add https://github.com/AeonDave/malskill --skill gitleaks-aeondave
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gitleaks
Source: https://github.com/AeonDave/malskill/tree/main/offensive-tools/cloud/gitleaks
Command: npx skills add https://github.com/AeonDave/malskill --skill gitleaks-aeondave

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill identifies and flags hardcoded secrets such as API keys, tokens, and credentials within git repositories and files, preventing potential security breaches.

Core Features & Use Cases

  • Secret Detection: Scans git repositories (including history) and individual files for sensitive information.
  • CI/CD Integration: Can be integrated into pipelines to automatically fail builds upon detecting secrets.
  • Customizable Rules: Supports custom rule configurations for specific internal patterns.
  • Use Case: Before merging code, use this Skill to scan the commit history and staged files for any accidentally committed API keys.

Quick Start

Scan the current git repository for hardcoded secrets and display verbose output.

Frequently Asked Questions about gitleaks

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

FAQPage Schema
How do I scan git history for hardcoded API keys and credentials?▼

This Skill detects hardcoded API keys by scanning git repositories, including commit history and staged files, to identify leaked credentials and prevent security breaches.

Can I integrate secret detection into CI pipelines to fail builds automatically?▼

Yes, this Skill integrates into CI pipelines to automatically fail builds upon detecting hardcoded secrets, API keys, and credentials in source code or commit history.

Do I need a Go binary to detect custom secrets in source code?▼

Yes, custom secret detection requires a Go binary and supports custom rule configurations to identify specific internal credential patterns within git repositories and files.

What is the best way to find leaked tokens in code before merging?▼

The best way to find leaked tokens before merging is to scan staged files and commit history for accidentally committed API keys, ensuring sensitive information is flagged during code reviews.

Does this code scanning tool support custom rule configurations for internal patterns?▼

Yes, this code scanning tool supports custom rule configurations to define specific patterns for detecting internal credentials and secrets within git repositories and files.

What output formats are supported when scanning repositories for secrets?▼

When scanning repositories for secrets, the Skill supports various output formats and verbose display options for security audits and pre-engagement reconnaissance to identify leaked credentials.

Related Skills

Explore More Software Engineering Skills→
EdanStarfireEdanStarfire
15

github-authenticator

Authenticate GitHub CLI credentials and troubleshoot authentication failures via gh commands.

Community
Intermediate
allanninalallanninal
1

sarif-parsing

Parse and analyze SARIF files from security scan results.

Community
Intermediate
logo-solutionslogo-solutions

ci-cd-and-automation

Automate CI/CD pipeline setup and enforcement for GitHub Actions workflows.

Official
Advanced
cosmixcosmix
53

security-scan

Detect secrets, dependency vulnerabilities, and misconfigurations in codebases.

Community
Advanced