ghost-scan-deps — Claude Code skill: what it does, how to install
An SCA orchestration skill that scans lockfiles for CVEs, evaluates vulnerability exploitability, and produces actionable remediation reports.
npx skills add ghostsecurity/skills --skill ghost-scan-deps -a claude-code
npx skills add ghostsecurity/skills --skill scan-deps -a claude-codeWhat ghost-scan-deps does
ghost-scan-deps acts as a top-level orchestrator for Software Composition Analysis (SCA). It searches the repository for dependency lockfiles such as package-lock.json, yarn.lock, go.mod, or Gemfile.lock to check them against known CVEs.
Instead of handling tasks directly, the orchestrator delegates steps to subagents via the Task tool. It installs the wraith scanner binary into ~/.ghost/bin/wraith, discovers lockfiles, runs detection, and spins up parallel analyzers to evaluate whether candidate vulnerabilities are exploitable. Scan artifacts and findings are saved under ~/.ghost/repos/.
The skill requires Bash access for directory setup and binary installation. If no lockfiles exist in the repository, the orchestrator immediately jumps to the summary step without running scans.
What it helps with
- detect known CVEs inside dependency lockfiles
- assess the exploitability of detected package vulnerabilities
- generate structured security findings with remediation steps
- inspect package-lock.json, yarn.lock, go.mod, or Gemfile.lock
Example prompts for the agent
- Scan our dependency lockfiles for known vulnerabilities and CVEs
- Run an SCA security audit on this repository
- Check package-lock.json for vulnerable dependencies and show remediation steps
How to install ghost-scan-deps
1Skills CLI (Vercel)
npx skills add ghostsecurity/skills --skill ghost-scan-deps -a claude-codenpx skills add ghostsecurity/skills --skill scan-deps -a claude-code2Manually: put the files in place
~/.claude/skills/scan-deps/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/scan-deps/
1Skills CLI (Vercel)
npx skills add ghostsecurity/skills --skill scan-deps -a codex2Manually: put the files in place
.agents/skills/scan-deps/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ghostsecurity/skills --skill scan-deps -a cursor2Manually: put the files in place
.cursor/skills/scan-deps/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ghostsecurity/skills scan-deps2Manually: put the files in place
.github/skills/scan-deps/SKILL.md1Skills CLI (Vercel)
npx skills add ghostsecurity/skills --skill scan-deps -a gemini-cli2Platform CLI
gemini skills install https://github.com/ghostsecurity/skills --path plugins/ghost/skills/scan-depsManually: put the files in place
.devin/skills/scan-deps/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ghostsecurity/skills --skill scan-deps -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about ghost-scan-deps
How to install ghost-scan-deps in Claude Code?
Run npx skills add ghostsecurity/skills --skill ghost-scan-deps -a claude-code in your terminal.
What does ghost-scan-deps do?
It discovers repository lockfiles, executes the wraith scanner to spot CVEs, and uses subagents to determine whether vulnerabilities are exploitable before reporting fixes.
What external tool does ghost-scan-deps rely on?
The skill relies on the wraith binary, which the setup agent installs directly to ~/.ghost/bin/wraith (or wraith.exe on Windows).
Source text
SKILL.md · Apache-2.0
---
name: "ghost-scan-deps"
description: |
Ghost Security - Software Composition Analysis (SCA) scanner. Scans dependency lockfiles for known vulnerabilities, identifies CVEs, and generates findings with severity levels and remediation guidance. Use when the user asks about dependency vulnerabilities, vulnerable packages, CVE checks, security audits of dependencies, or wants to scan lockfiles like package-lock.json, yarn.lock, go.mod, or Gemfile.lock.
allowed-tools: Read, Glob, Grep, Bash, Task, TodoRead, TodoWrite
argument-hint: "[path-to-scan]"
license: apache-2.0
metadata:
version: 1.1.0
---
# Ghost Security SCA Scanner — Orchestrator
You are the top-level orchestrator for Software Composition Analysis (SCA) 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>/deps`
- **short_sha**: `git rev-parse --short HEAD` (falls back to `YYYYMMDD` for non-git dirs)
$ARGUMENTS
Any values provided above override the defaults.
---
## Execution
1. **Setup** — compute paths and create output directories
2. **Initialize Wraith** — install the wraith binary
3. **Discover Lockfiles** — find all dependency lockfiles in the repo
4. **Scan for Vulnerabilities** — run wraith against each lockfile
5. **Analyze Candidates** — assess exploitability of each candidate
6. **Summarize Results** — generate the final scan report
### Step 0: Setup
Run this Bash command to compute the repo-specific output directory, create it, and locate the skill files:
```
repo_name=$(basename "$(pwd)") && remote_url=$(git remote get-url origin 2>/dev/null || pwd) && short_hash=$(printf '%s' "$remote_url" | git hash-object --stdin | cut -c1-8) && repo_id="${repo_name}-${short_hash}" && short_sha=$(git rev-parse --short HEAD 2>/dev/null || date +%Y%m%d) && ghost_repo_dir="$HOME/.ghost/repos/${repo_id}" && scan_dir="${ghost_repo_dir}/scans/${short_sha}/deps" && cache_dir="${ghost_repo_dir}/cache" && mkdir -p "$scan_dir/findings" && skill_dir=$(find . -path '*skills/scan-deps/SKILL.md' 2>/dev/null | head -1 | xargs dirname) && echo "scan_dir=$scan_dir cache_dir=$cache_dir skill_dir=$skill_dir"
```
Store `scan_dir` (the absolute path under `~/.ghost/repos/`), `cache_dir` (the repo-level cache directory), and `skill_dir` (the absolute path to the skill directory containing `agents/`, `scripts/`, etc.).
After this step, your only remaining tool is Task. Do not use Bash, Read, Grep, Glob, or any other tool for Steps 1–5.
### Step 1: Initialize Wraith
Call the Task tool to initialize the wraith binary:
```json
{
"description": "Initialize wraith binary",
"subagent_type": "general-purpose",
"prompt": "You are the init agent. Read and follow the instructions in <skill_dir>/agents/init/agent.md.\n\n## Inputs\n- skill_dir: <skill_dir>"
}
```
The init agent installs wraith to `~/.ghost/bin/wraith` (or `wraith.exe` on Windows).
### Step 2: Discover Lockfiles
Call the Task tool to discover lockfiles in the repository:
```json
{
"description": "Discover lockfiles",
"subagent_type": "general-purpose",
"prompt": "You are the discover agent. Read and follow the instructions in <skill_dir>/agents/discover/agent.md.\n\n## Inputs\n- repo_path: <repo_path>\n- scan_dir: <scan_dir>"
}
```
The discover agent finds all lockfiles (go.mod, package-lock.json, etc.) and writes `<scan_dir>/lockfiles.json`.
**If lockfile count is 0**: Skip to Step 5 (Summarize) with no lockfiles found.
### Step 3: Scan for Vulnerabilities
Call the Task tool to run the wraith scanner:
```json
{
"description": "Scan for vulnerabilities",
"subagent_type": "general-purpose",
"prompt": "You are the scan agent. Read and follow the instructions in <skill_dir>/agents/scan/agent.md.\n\n## Inputs\n- repo_path: <repo_path>\n- scan_dir: <scan_dir>"
}
```
The scan agent executes wraith for each lockfile and writes `<scan_dir>/candidates.json`.
**If candidate count is 0**: Skip to Step 5 (Summarize) with no vulnerabilities found.
### Step 4: Analyze Candidates
Call the Task tool to analyze the vulnerability candidates:
```json
{
"description": "Analyze vulnerability candidates",
"subagent_type": "general-purpose",
"prompt": "You are the analysis agent. Read and follow the instructions in <skill_dir>/agents/analyze/agent.md.\n\n## Inputs\n- repo_path: <repo_path>\n- scan_dir: <scan_dir>\n- skill_dir: <skill_dir>\n- cache_dir: <cache_dir>"
}
```
The analysis agent spawns parallel analyzers for each candidate to assess exploitability and writes finding files to `<scan_dir>/findings/`.
### Step 5: Summarize Results
Call the Task tool to summarize the findings:
```json
{
"description": "Summarize scan results",
"subagent_type": "general-purpose",
"prompt": "You are the summarize agent. Read and follow the instructions in <skill_dir>/agents/summarize/agent.md.\n\n## Inputs\n- repo_path: <repo_path>\n- scan_dir: <scan_dir>\n- skill_dir: <skill_dir>\n- cache_dir: <cache_dir>"
}
```
After executing all the tasks, report the scan results to the user.
---
## Error Handling
If any Task call fails, retry it **once**. If it fails again, stop and report the failure.
© ghostsecurity · Apache-2.0 · ghostsecurity/skills