Gitleaks Auto Scan

Automate secret scanning with gitleaks — detect API keys, passwords, tokens before incidents.

Install
cmdop skills install agensi-gitleaks-auto-scan

Gitleaks Auto Scan is a skill published by agensi that automates secret scanning using Gitleaks. Its stated purpose is to detect exposed credentials — API keys, passwords, and tokens — in code before they lead to security incidents. According to its short description, it wraps Gitleaks scanning into an automated workflow that an agent can invoke as part of a development or CI-adjacent process.

The skill requires Claude Code CLI to run. No tools are listed in this registry record, so the specific operations exposed to an agent are not documented here. Based solely on the stated short description, the capability is oriented toward proactive credential leak detection rather than general code analysis or repository management.

The long description in the upstream record describes a multi-source document merging workflow, which does not match the skill’s name or short description. This inconsistency means the long description cannot be treated as a reliable source of facts for this capability. Developers should treat the short description — secret scanning automation with Gitleaks — as the authoritative statement of scope.

This skill is appropriate when an agent needs to scan code or files for accidentally committed secrets before a deployment or code review step. It is not suitable for teams that do not use Claude Code CLI, as that is a stated dependency. It also does not appear to cover general static analysis, vulnerability scanning beyond secrets, or direct integration with source control platforms based on the available facts.

Use cases

  • Scan a codebase for accidentally committed API keys before a release
  • Detect hardcoded passwords or tokens in files prior to code review
  • Automate secret detection as part of an agent-driven development workflow

When to use it

  • An agent needs to check code for exposed credentials before deployment
  • The team wants automated secret scanning without manual Gitleaks invocation
  • Claude Code CLI is already part of the development environment

When not to use it

  • Claude Code CLI is not available or not permitted in the environment
  • The requirement is for general static analysis or broad vulnerability scanning beyond secrets
  • Direct integration with a specific source control platform API is needed
  • A fully documented tool list is required before adoption, as no tools are listed in this record