vulnerability-scanner

Name: vulnerability-scanner
Availability: InStock
Author: skeletorflet

Analyze dependencies, secrets, and code patterns to generate prioritized vulnerability reports.

7|1|Updated Mar 28, 2026

Search Tags:#security #vulnerability #owasp #threat-modeling #supply-chain #risk-prioritization #code-scan

Ready to run

npx skills add https://github.com/skeletorflet/opencode-kit --skill vulnerability-scanner-skeletorflet

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vulnerability-scanner
Source: https://github.com/skeletorflet/opencode-kit/tree/main/.opencode/skills/vulnerability-scanner
Command: npx skills add https://github.com/skeletorflet/opencode-kit --skill vulnerability-scanner-skeletorflet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Security vulnerabilities in codebases are often hidden, scattered across dependencies, secrets, and code patterns, making it hard to triage and remediate effectively.

Core Features & Use Cases

Automated dependency auditing to detect known vulnerabilities and supply chain risks during CI/CD.
Secrets and credential exposure scanning to prevent leakage in code and configuration files.
Dangerous code pattern detection and security configuration checks to surface high-risk patterns before deployment.

Quick Start

Install or configure the scanner and run a project-wide audit to generate a prioritized vulnerability report.

Frequently Asked Questions about vulnerability-scanner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I identify and prioritize security vulnerabilities in my codebase?▼

To identify and prioritize security vulnerabilities, scan your codebase for unsafe patterns, exposed secrets, and dependency risks. This generates a structured report with severity ratings and mitigation guidance to direct remediation efforts.

Can I detect supply chain risks and exposed credentials during CI/CD pipelines?▼

Yes, you can detect supply chain risks and exposed credentials during CI/CD. Automated dependency auditing and secrets scanning check code and configurations to prevent leakage before deployment.

What is the best way to map the attack surface and perform threat modeling for a project?▼

Mapping the attack surface and performing threat modeling involves analyzing dangerous code patterns and insecure configurations. This surfaces high-risk areas to guide security checks across development workflows.

Does this automated code scan check for insecure configurations and dangerous code patterns?▼

Yes, this automated code scan checks for insecure configurations and dangerous code patterns. It enforces security checks to identify high-risk exposures before deployment.

When do I need to run a dependency audit for known vulnerabilities?▼

You need to run a dependency audit for known vulnerabilities during CI/CD pipelines to catch supply chain risks early. It detects known flaws before deployment.

What is the limitation of relying solely on automated security checks?▼

Automated security checks identify known dangerous patterns and exposed secrets but may miss complex logic flaws. They guide remediation priorities but require human review for complete threat modeling.