Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
aj-geddes avatar

Vulnerability Scanning

  • 541 installs
  • 305 repo stars
  • Updated March 4, 2026
  • aj-geddes/useful-ai-prompts

vulnerability-scanning is a Claude Code skill that guides dependency, configuration, and code security scans for developers who must catch CVEs and OWASP risks before release.

About

vulnerability-scanning is a Claude Code skill from aj-geddes/useful-ai-prompts that structures agent-led security review before production deployment. The skill directs scans across third-party dependencies for known CVEs, configuration files for misconfigurations, and application source for OWASP-class unsafe patterns. Developers reach for vulnerability-scanning when preparing a release candidate, responding to security audit requests, or hardening a codebase without a dedicated AppSec engineer in the loop. It functions as a prompt-driven checklist that channels the agent through systematic discovery and reporting of exploitable weaknesses rather than ad-hoc grep searches.

  • CVE-oriented scan prompts
  • OWASP-aligned review flows
  • Pre-release security gate
  • Agent-driven code inspection
  • Dependency and config triage

Vulnerability Scanning by the numbers

  • 541 all-time installs (skills.sh)
  • Ranked #502 of 2,203 Security skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/aj-geddes/useful-ai-prompts --skill vulnerability-scanning

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs541
repo stars305
Last updatedMarch 4, 2026
Repositoryaj-geddes/useful-ai-prompts

How do you scan code for CVEs before release?

Guide agents through dependency, config, and code scans to surface CVEs, OWASP risks, and unsafe patterns before production release.

Who is it for?

Developers performing pre-release security review who need structured dependency, config, and code vulnerability coverage.

Skip if: Formal penetration testing engagements or compliance certifications that require licensed third-party auditors.

When should I use this skill?

The developer asks for vulnerability scans, CVE checks, OWASP review, or security hardening before shipping.

What you get

Security scan findings listing CVEs, OWASP risk categories, misconfigured settings, and unsafe code patterns with remediation notes.

  • CVE and vulnerability findings report
  • OWASP risk assessment notes
  • Remediation recommendations

Files

SKILL.mdMarkdownGitHub ↗

Vulnerability Scanning

Table of Contents

Overview

Systematically identify security vulnerabilities in applications, dependencies, and infrastructure using automated scanning tools and manual security assessments.

When to Use

  • Pre-deployment security checks
  • Continuous security monitoring
  • Compliance audits (PCI-DSS, SOC 2)
  • Dependency vulnerability detection
  • Container security scanning
  • Infrastructure security assessment

Quick Start

Minimal working example:

// scanner.js - Comprehensive vulnerability scanning
const { exec } = require("child_process");
const util = require("util");
const fs = require("fs").promises;

const execPromise = util.promisify(exec);

class VulnerabilityScanner {
  constructor() {
    this.results = {
      dependencies: [],
      code: [],
      docker: [],
      secrets: [],
    };
  }

  async scanDependencies() {
    console.log("Scanning dependencies with npm audit...");

    try {
      const { stdout } = await execPromise("npm audit --json");
      const auditResults = JSON.parse(stdout);

      for (const [name, advisory] of Object.entries(
// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

GuideContents
Node.js Vulnerability ScannerNode.js Vulnerability Scanner
Python OWASP ScannerPython OWASP Scanner
CI/CD Integration - GitHub ActionsCI/CD Integration - GitHub Actions

Best Practices

✅ DO

  • Automate scans in CI/CD
  • Scan dependencies regularly
  • Use multiple scanning tools
  • Set severity thresholds
  • Track vulnerability trends
  • Scan containers and images
  • Monitor CVE databases
  • Document false positives

❌ DON'T

  • Skip vulnerability scanning
  • Ignore low severity issues
  • Trust single scanning tool
  • Bypass security gates
  • Commit secrets to repos

Related skills

How it compares

Pick vulnerability-scanning over generic code review skills when the goal is pre-release CVE, OWASP, and configuration security coverage.

FAQ

What does vulnerability-scanning check?

The vulnerability-scanning skill guides agents through dependency scans for CVEs, configuration reviews for misconfigurations, and code analysis for OWASP risks and unsafe patterns. It targets issues that should be resolved before a production release.

When should I invoke vulnerability-scanning?

Invoke vulnerability-scanning before shipping to production, during security review sprints, or when audit findings require systematic CVE and OWASP coverage. The skill structures agent prompts rather than replacing dedicated penetration testing tools.

Securityauditappsec

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.