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

Vulnerability Scanner

  • 1.1k installs
  • 44k repo stars
  • Updated July 27, 2026
  • sickn33/antigravity-awesome-skills

vulnerability-scanner is a Claude Code skill that systematically scans projects for OWASP-aligned vulnerabilities, maps attack surfaces, and prioritizes security risks before release.

About

vulnerability-scanner is a community skill from sickn33/antigravity-awesome-skills that applies OWASP 2025 principles, supply chain security checks, attack surface mapping, and risk prioritization before shipping code. It bundles scripts/security_scan.py for automated validation via python scripts/security_scan.py <project_path> plus reference checklists covering OWASP Top 10 and authentication patterns. Developers reach for vulnerability-scanner when they need structured pre-release security review with executable scanning rather than ad-hoc grep for secrets or generic security tips.

  • Applies 2025 OWASP Top 10 principles including Broken Access Control and Supply Chain Security
  • Includes automated validation via scripts/security_scan.py for any project path
  • Provides ready-to-use checklists covering OWASP, Auth, API, and Data Protection
  • Teaches attacker mindset with Assume Breach, Zero Trust, Defense in Depth, Least Privilege and Fail Secure
  • Delivers structured threat modeling questions before every scan

Vulnerability Scanner by the numbers

  • 1,081 all-time installs (skills.sh)
  • +24 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #365 of 2,209 Security skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill vulnerability-scanner

Add your badge

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

Listed on Skillselion
Installs1.1k
repo stars44k
Security audit3 / 3 scanners passed
Last updatedJuly 27, 2026
Repositorysickn33/antigravity-awesome-skills

How do you scan a codebase for OWASP vulnerabilities?

Systematically scan projects for OWASP-aligned vulnerabilities, map attack surfaces, and prioritize risks before shipping.

Who is it for?

Developers performing pre-ship security audits who want OWASP 2025-aligned checklists plus an automated Python scanner script.

Skip if: Penetration testing engagements requiring live exploitation tools or compliance certification workflows without codebase access.

When should I use this skill?

The user asks to scan for vulnerabilities, review OWASP risks, map attack surfaces, or validate security before shipping.

What you get

Prioritized vulnerability report, completed OWASP checklists, and security_scan.py validation output.

  • Prioritized risk list
  • Completed security checklists
  • Scanner script output

By the numbers

  • Bundles scripts/security_scan.py for automated project validation
  • References OWASP Top 10 and authentication checklists in checklists.md

Files

SKILL.mdMarkdownGitHub ↗

Vulnerability Scanner

Think like an attacker, defend like an expert. 2025 threat landscape awareness.

🔧 Runtime Scripts

Execute for automated validation:

ScriptPurposeUsage
scripts/security_scan.pyValidate security principles appliedpython scripts/security_scan.py <project_path>

📋 Reference Files

FilePurpose
checklists.mdOWASP Top 10, Auth, API, Data protection checklists

---

1. Security Expert Mindset

Core Principles

PrincipleApplication
Assume BreachDesign as if attacker already inside
Zero TrustNever trust, always verify
Defense in DepthMultiple layers, no single point
Least PrivilegeMinimum required access only
Fail SecureOn error, deny access

Threat Modeling Questions

Before scanning, ask: 1. What are we protecting? (Assets) 2. Who would attack? (Threat actors) 3. How would they attack? (Attack vectors) 4. What's the impact? (Business risk)

---

2. OWASP Top 10:2025

Risk Categories

RankCategoryThink About
A01Broken Access ControlWho can access what? IDOR, SSRF
A02Security MisconfigurationDefaults, headers, exposed services
A03Software Supply Chain 🆕Dependencies, CI/CD, build integrity
A04Cryptographic FailuresWeak crypto, exposed secrets
A05InjectionUser input → system commands
A06Insecure DesignFlawed architecture
A07Authentication FailuresSession, credential management
A08Integrity FailuresUnsigned updates, tampered data
A09Logging & AlertingBlind spots, no monitoring
A10Exceptional Conditions 🆕Error handling, fail-open states

2025 Key Changes

2021 → 2025 Shifts:
├── SSRF merged into A01 (Access Control)
├── A02 elevated (Cloud/Container configs)
├── A03 NEW: Supply Chain (major focus)
├── A10 NEW: Exceptional Conditions
└── Focus shift: Root causes > Symptoms

---

3. Supply Chain Security (A03)

Attack Surface

VectorRiskQuestion to Ask
DependenciesMalicious packagesDo we audit new deps?
Lock filesIntegrity attacksAre they committed?
Build pipelineCI/CD compromiseWho can modify?
RegistryTyposquattingVerified sources?

Defense Principles

  • Verify package integrity (checksums)
  • Pin versions, audit updates
  • Use private registries for critical deps
  • Sign and verify artifacts

---

4. Attack Surface Mapping

What to Map

CategoryElements
Entry PointsAPIs, forms, file uploads
Data FlowsInput → Process → Output
Trust BoundariesWhere auth/authz checked
AssetsSecrets, PII, business data

Prioritization Matrix

Risk = Likelihood × Impact

High Impact + High Likelihood → CRITICAL
High Impact + Low Likelihood  → HIGH
Low Impact + High Likelihood  → MEDIUM
Low Impact + Low Likelihood   → LOW

---

5. Risk Prioritization

CVSS + Context

FactorWeightQuestion
CVSS ScoreBase severityHow severe is the vuln?
EPSS ScoreExploit likelihoodIs it being exploited?
Asset ValueBusiness contextWhat's at risk?
ExposureAttack surfaceInternet-facing?

Prioritization Decision Tree

Is it actively exploited (EPSS >0.5)?
├── YES → CRITICAL: Immediate action
└── NO → Check CVSS
         ├── CVSS ≥9.0 → HIGH
         ├── CVSS 7.0-8.9 → Consider asset value
         └── CVSS <7.0 → Schedule for later

---

6. Exceptional Conditions (A10 - New)

Fail-Open vs Fail-Closed

ScenarioFail-Open (BAD)Fail-Closed (GOOD)
Auth errorAllow accessDeny access
Parsing failsAccept inputReject input
TimeoutRetry foreverLimit + abort

What to Check

  • Exception handlers that catch-all and ignore
  • Missing error handling on security operations
  • Race conditions in auth/authz
  • Resource exhaustion scenarios

---

7. Scanning Methodology

Phase-Based Approach

1. RECONNAISSANCE
   └── Understand the target
       ├── Technology stack
       ├── Entry points
       └── Data flows

2. DISCOVERY
   └── Identify potential issues
       ├── Configuration review
       ├── Dependency analysis
       └── Code pattern search

3. ANALYSIS
   └── Validate and prioritize
       ├── False positive elimination
       ├── Risk scoring
       └── Attack chain mapping

4. REPORTING
   └── Actionable findings
       ├── Clear reproduction steps
       ├── Business impact
       └── Remediation guidance

---

8. Code Pattern Analysis

High-Risk Patterns

PatternRiskLook For
String concat in queriesInjection"SELECT * FROM " + user_input
Dynamic code executionRCEeval(), exec(), Function()
Unsafe deserializationRCEpickle.loads(), unserialize()
Path manipulationTraversalUser input in file paths
Disabled securityVariousverify=False, --insecure

Secret Patterns

TypeIndicators
API Keysapi_key, apikey, high entropy
Tokenstoken, bearer, jwt
Credentialspassword, secret, key
CloudAWS_, AZURE_, GCP_ prefixes

---

9. Cloud Security Considerations

Shared Responsibility

LayerYou OwnProvider Owns
Data
Application
OS/RuntimeDependsDepends
Infrastructure

Cloud-Specific Checks

  • IAM: Least privilege applied?
  • Storage: Public buckets?
  • Network: Security groups tightened?
  • Secrets: Using secrets manager?

---

10. Anti-Patterns

❌ Don't✅ Do
Scan without understandingMap attack surface first
Alert on every CVEPrioritize by exploitability + asset
Ignore false positivesMaintain verified baseline
Fix symptoms onlyAddress root causes
Scan once before deployContinuous scanning
Trust third-party deps blindlyVerify integrity, audit code

---

11. Reporting Principles

Finding Structure

Each finding should answer: 1. What? - Clear vulnerability description 2. Where? - Exact location (file, line, endpoint) 3. Why? - Root cause explanation 4. Impact? - Business consequence 5. How to fix? - Specific remediation

Severity Classification

SeverityCriteria
CriticalRCE, auth bypass, mass data exposure
HighData exposure, privilege escalation
MediumLimited scope, requires conditions
LowInformational, best practice

---

Remember: Vulnerability scanning finds issues. Expert thinking prioritizes what matters. Always ask: "What would an attacker do with this?"

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Related skills

How it compares

Use vulnerability-scanner for structured OWASP pre-ship audits with a bundled Python scanner rather than secret-only grep skills.

FAQ

How do you run the vulnerability-scanner automation script?

vulnerability-scanner executes scripts/security_scan.py with python scripts/security_scan.py <project_path> to validate that security principles and OWASP-aligned checks are applied across the project.

Which security frameworks does vulnerability-scanner cover?

vulnerability-scanner aligns with OWASP 2025, OWASP Top 10 checklists, authentication patterns, and supply chain security principles for attack surface mapping and risk prioritization.

Is Vulnerability Scanner safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

Securityauditappsec

This week in AI coding

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

unsubscribe anytime.