@ghostsecurity

ghost-scan-deps orchestrates software composition analysis by spawning subagents to discover lockfiles, scan for vulnerabilities with wraith, analyze exploitability, and generate findings reports.

ghost-scan-secrets orchestrates multi-stage secrets detection by delegating setup, poltergeist initialization, candidate scanning, analysis, and summarization to specialized subagents via the task tool.

ghost-repo-context walks a codebase to detect project structure and dependencies, writing findings to repo.md. works without delegation but lacks clarity on what output actually gets produced and how edge cases are handled.

ghost-scan-code plans and executes targeted static analysis scans across repositories, selecting vulnerability vectors based on scan depth (quick, balanced, full) and optional argument overrides for customization.

ghost-report aggregates findings from multiple security scanners into a single prioritized report, with caching at commit level and severity-based sorting, but lacks clear procedural steps and concrete trigger patterns.

ghost-proxy wraps reaper, a mitm proxy for intercepting http/https traffic during security testing. captures and inspects request/response pairs but lacks actionable procedures and failure handling.

This skill should be used when the user asks to "validate a finding", "check if a vulnerability is real", "triage a security finding", "confirm a…