Agent skill · security · ghostsecurity
ghost-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.
Why this skill is useful
Adds a comprehensive executable script that aggregates and prioritizes security findings from multiple scans, providing a unique capability not available in standard tools.
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
Combined Security Report You aggregate findings from all scan skills (scan-deps, scan-secrets, scan-code) into a single prioritized report. Do all work yourself — do not spawn subagents or delegate. $ARGUMENTS --- Step 0: Setup Run this Bash command to compute paths: Store scansdir (commit-level scan directory), cachedir, and skilldir. --- Cache Check If <scansdir>/report.md already exists, show: And stop. Do not regenerate it. --- Step 1: Read Repo Context Read <cachedir>/repo.md if it exists. Extract: Business criticality Sensitive data types Component map If it does not exist, continue without it — this is not an error. --- Step 2: Discover Scan Results List the contents of <scansdir> to see which scan-type directories exist. Recognized types: deps/ — SCA / dependency vulnerability scan secrets/ — secrets and credentials scan code/ — code security scan (SAST) If none of these directories exist, report an error: And stop. --- Step 3: Collect Findings For each scan type that exists, glob <scansdir>/<type>/findings/.md and read each finding file in full. Retain the complete markdown body of every finding — the report will inline this content directly so readers never need to open individual finding files. From each finding, also extract these metadata fields for filtering and sorting: ID — from ## Metadata → ID Type — the scan type (deps, secrets, or code) Severity — from ## Metadata → Severity (high, medium, low) Status — from ## Metadata → Status (e.g., confirmed-exploitable, unverified, verified, rejected, clean) --- Step 4: Filter and Sort Filter: Keep only high-confidence findings: For deps findings: status is confirmed-exploitable For secrets findings: status is NOT clean and NOT rejected For code findings: status is verified or unverified (NOT rejected) Exclude any finding with status clean, rejected, or false-positive. Sort the remaining findings: 1. By severity: high first, then medium, then low 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills ghostsecurity/report