Sweep GitHub for leaked secrets and exposed credentials with git-hound
Search public GitHub broadly for leaked secrets and triage exposures when the workflow is recon and remediation, not generic secret scanning.
Prerequisites
git-hound binary, GitHub token or code search access, and operator-defined dork queries
Installation
Choose whichever fits your setup:
- Copy this skill folder into your local skills directory.
- Clone the repo and symlink or copy the skill into your agent workspace.
- Add the repo as a git submodule if you manage shared skills centrally.
- Install it through your internal provisioning or packaging workflow.
- Download the folder directly from GitHub and place it in your skills collection.
Install command or upstream instructions:
Download git-hound from GitHub Releases, configure the required GitHub access in config.yml, then run dork or keyword searches to scan matching repositories and histories for leaked secrets.