← ClaudeAtlas

security-scanlisted

Use when a user asks to scan a repository for dependency vulnerabilities, insecure code patterns, CVEs, or OWASP Top 10 risks.
Ray0907/security-scan · ★ 21 · AI & Automation · score 82
Install: claude install-skill Ray0907/security-scan
# Security Scan Produce an evidence-backed security assessment without changing application code or dependencies. ## Boundaries - Treat scanning as read-only. Do not install tools, update advisory databases, build images, run project scripts, or modify global client settings without explicit approval. - Never report a clean scan when a tool failed, was missing, or could not cover the target. - Never copy secret values into chat or reports. Follow [the reporting and redaction contract](references/REPORTING.md). - Scan every detected project in a monorepo, not only the repository root. ## Interpret the Request Default to dependency and code scanning. Apply these modes before running tools: - `--deps-only`: skip Semgrep. - `--code-only`: skip dependency scanners. - `--owasp A01` through `A10`: retain only findings mapped to that 2025 category. - `--severity critical,high`: filter after normalizing scanner output. - `--export-bypass`: read the reporting reference and export reviewed false positives only. - `--auto-remind`: explain that reminders are client-specific. Do not claim they are enabled or write client configuration until the user chooses a supported hook or automation. Reject incompatible `--deps-only` and `--code-only` requests instead of guessing. ## Workflow 1. Record the repository path, Git commit, requested modes, scope, and exclusions. 2. Read [the scanner contract](references/SCANNERS.md). Build the dependency plan, repeating `--exclude` for ea