ghost-scan-secrets
Automated secrets scanner that detects hardcoded API keys, tokens, passwords, and sensitive data in codebases.
- Scans repositories for leaked credentials and generates findings with severity levels and remediation guidance
- Uses the poltergeist binary to identify secret candidates, then analyzes and confirms each one through parallel subagents
- Stores scan results and findings in a repo-specific cache directory under
~/.ghost/repos/with git-based versioning - Orchestrates multi-step workflow: setup, initialization, scanning, candidate analysis, and summary report generation
Ghost Security Secrets Scanner — Orchestrator
You are the top-level orchestrator for secrets scanning. Your ONLY job is to call the Task tool to spawn subagents to do the actual work. Each step below gives you the exact Task tool parameters to use. Do not do the work yourself.
Defaults
- repo_path: the current working directory
- scan_dir:
~/.ghost/repos/<repo_id>/scans/<short_sha>/secrets - short_sha:
git rev-parse --short HEAD(falls back toYYYYMMDDfor non-git dirs)
$ARGUMENTS
Any values provided above override the defaults.
Execution
More from ghostsecurity/skills
ghost-scan-code
Ghost Security - SAST code scanner. Finds security vulnerabilities in source code by planning and executing targeted scans for issues like SQL injection, XSS, BOLA, BFLA, SSRF, and other OWASP categories. Supports applications (backend, frontend, mobile) and libraries (prototype pollution, unsafe deserialization, ReDoS, path traversal, zip slip). Use when the user asks for a code security audit, SAST scan, vulnerability scan of source code, or wants to find security flaws in a codebase or library.
2.1Kghost-scan-deps
|
1.6Kghost-proxy
Starts and controls the reaper MITM proxy to capture, inspect, search, and replay HTTP/HTTPS traffic between clients and servers. Capabilities include starting/stopping the proxy scoped to specific domains, viewing captured request/response logs, searching traffic by method/path/status/host, and inspecting full raw HTTP entries for security analysis. Use when the user asks to "start the proxy", "capture traffic", "intercept requests", "inspect HTTP traffic", "search captured requests", or "view request/response".
1.4Kghost-validate
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 vulnerability", "determine if a finding is a true positive or false positive", or provides a security finding for review. It validates security vulnerability findings by tracing data flows, verifying exploit conditions, analyzing security controls, and optionally testing attack vectors against a live application.
1.4Kghost-report
Ghost Security — combined security report. Aggregates findings from all scan skills (scan-deps, scan-secrets, scan-code) into a single prioritized report focused on the highest risk, highest confidence issues. Use when the user requests a security overview, vulnerability summary, full security audit, or combined scan results.
1.4Kghost-repo-context
Scans directory structure, detects projects, maps dependencies, and documents code organization into a repo.md file. Use when the user needs a codebase overview, project structure map, or repository context before security analysis.
1.4K