security-scanning
Use when checking code for vulnerabilities, linting shell scripts, scanning containers or IaC for security issues, or managing encrypted secrets
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill security-scanning --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Security Scanning ## When to Use - Scanning a project directory for known vulnerabilities (CVEs) - Scanning a container image before deployment - Scanning Infrastructure-as-Code (Terraform, CloudFormation) for misconfigurations - Linting shell scripts for bugs, pitfalls, and unsafe patterns - Encrypting or decrypting secrets stored in YAML/JSON config files - Checking dependencies for known secu
What does the security-scanning skill do?
Use when checking code for vulnerabilities, linting shell scripts, scanning containers or IaC for security issues, or managing encrypted secrets
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill security-scanning --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.