Individual skill
security-scan
Use when automated scanners drive a security sweep of a repo or app — SAST, dependency/lockfile CVEs, secrets in the tree or git history, IaC misconfig — and the raw output has to become one deduped, exploitability-ranked report CI can gate on. NOT threat-modeling, OWASP design reasoning, or hand-authoring the fix (that is `secure-coding`).
skills/security-scan/SKILL.md
Source commit d9d6bb338f66cc1e23998585e580a0ea45bbcb82
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 10, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 578
- Repository last updated
- Nov 9, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- agentic-ai Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- claude-code Repository topic
- cli Repository topic
- cline Repository topic
- codex Repository topic
- coding-assistant Repository topic
- cursor Repository topic
- security Declared skill tag
- sast Declared skill tag
- sca Declared skill tag
- secrets Declared skill tag
- scanning Declared skill tag
- owasp Declared skill tag
- security Derived category
- engineering Derived category
- design Derived category
- security-application Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 11,179 bytesSKILL.mdcore · 11,179 bytesSKILL.mdcore · 11,179 bytesSKILL.mdcore · 11,179 bytesSKILL.mdcore · 11,179 bytesSKILL.mdcore · 11,179 bytesSKILL.mdcore · 11,179 bytesevals/README.mddoc · 909 bytesevals/cases.yamlasset · 3,096 bytesreferences/tools.mddoc · 4,059 bytesreferences/triage.mddoc · 3,853 bytesscripts/verify.shruns · 4,251 bytes
Read excerpt
# Security scan — orchestrate scanners, triage the noise, emit a gate
A **machine-first** vulnerability sweep. Point automated scanners at a codebase,
collect SARIF/JSON, then do the work that has actual value: dedupe cross-tool
overlap, rank by exploitability, and emit one gate artifact CI can act on. The
finding comes from a **tool run**, not a hunch — if you are reasoning about a
design or hand-writing a fix, that is [`secure-coding`](../secure-coding/SKILL.md),
not this skill.
Your job is orchestration + triage: every finding traces to a scanner run with a
`ruleId` and a source location, so the output is reproducible. Not eyeballing
code, not authoring patches.
**Read-only by default.** Scan, triage, report. Apply fixes (version bumps,