Ghost Scan Secrets

It uses an orchestrator pattern to spawn subagents that run a tool called Poltergeist against your codebase, then individually assess each candidate to cut down false positives. The findings get written to a structured directory under ~/.ghost with severity ratings and remediation guidance. It's built for when you need to audit a repo for leaked API keys, hardcoded passwords, or exposed .env values before they hit production. The agent architecture means it can parallelize analysis across candidates, which matters if you're scanning a large codebase. Outputs are organized by repo and commit hash, so you can track findings over time.