Agent skill · security · ghostsecurity
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.
Why this skill is useful
Adds executable scripts for planning and executing targeted SAST scans that are not commonly available in public documentation.
What it needs
Requires bash installed locally. About 3k tokens when loaded. Last updated 2026-03-11. 397 stars on the source repository.
What this skill does
Find Issues You find security issues in a repository. This skill plans which vulnerability vectors to scan, then executes those scans against each project. Inputs depth: quick (default), balanced, or full — override via $ARGUMENTS $ARGUMENTS Note: Arguments passed can be used to customize the scan workflow if provided. For example, if the user specifies a specific set of vectors, count of vectors, specific candidate files, areas to focus on, count of candidate files, etc., ensure the relevant details are passed to the relevant steps in the skill. Supporting files Loop script: scripts/loop.sh Scan criteria: criteria/index.yaml --- Step 1: Setup Compute the repo-specific output directory: 1. Read $cachedir/repo.md — if missing, run the repo-context skill first and then continue. 2. Read criteria/index.yaml to get the valid agent→vector mappings per project type 3. Set depth to quick if not provided 4. If depth is full, warn the user that a full scan uses significantly more tokens and ask them to confirm before proceeding. If they decline, fall back to balanced. --- Step 2: Plan Scans If $scandir/plan.md already exists, skip to the next step. Otherwise, run the planner using scripts/loop.sh: Use a 10-minute timeout. If the command times out, re-run it — the script resumes from where it left off. If it fails 3 times consecutively with the same error, stop and report the failure. Verify: $scandir/plan.md exists and contains at least one ## Project: section before proceeding. --- Step 3: Nominate Files If $scandir/nominations.md does not exist, generate it by reading $scandir/plan.md and for each project section (## Project: <basepath> (<type>)), parse the Recommended Scans table. For each row, extract the Agent and Vector columns. Write $scandir/nominations.md - one line per (project, agent, vector) combination. Skip projects with empty scan tables. If $scandir/nominations.md already exists, change every top level task - [x] to - [ ]. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills ghostsecurity/scan-code