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

Security Scan

  • 379 installs
  • 133 repo stars
  • Updated February 24, 2026
  • jwynia/agent-skills

security-scan is an agent skill that runs structured security scans on codebases or infrastructure configs before release to surface vulnerabilities, misconfigurations, and compliance gaps for developer remediation.

About

security-scan is a skill from jwynia/agent-skills that orchestrates structured security scanning across application code and configuration files before release. The agent follows a defined scan workflow to identify dependency CVEs, insecure defaults, exposed secrets patterns, and compliance gaps rather than ad-hoc grep searches. Developers invoke security-scan when preparing a release candidate, onboarding a inherited repo, or responding to audit requests. Output is organized findings with severity and remediation guidance suitable for ticket creation. The skill complements manual code review by systematically covering common OWASP and misconfiguration categories across the repository tree.

  • Vuln detection
  • Config review
  • Pre-release checks
  • Risk triage
  • Compliance hints

Security Scan by the numbers

  • 379 all-time installs (skills.sh)
  • +2 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #565 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/jwynia/agent-skills --skill security-scan

Add your badge

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

Listed on Skillselion
Installs379
repo stars133
Last updatedFebruary 24, 2026
Repositoryjwynia/agent-skills

How do you scan a codebase before release?

Run structured security scans on codebases or configs before release to surface vulnerabilities, misconfigurations, and compliance gaps for remediation.

Who is it for?

Developers preparing a release or audit who need a systematic security pass over code and configs beyond spot-checking individual files.

Skip if: Skip security-scan when you need certified penetration testing, runtime DAST against production URLs, or SOC2 auditor sign-off.

When should I use this skill?

User asks for a security scan, vulnerability review, or pre-release security audit of the repository or deployment configs.

What you get

Prioritized vulnerability report, misconfiguration list, compliance gap notes, and remediation recommendations.

Files

SKILL.mdMarkdownGitHub ↗

Security Scan

Comprehensive security vulnerability detection for codebases.

Quick Start

/security-scan                    # Full scan of current directory
/security-scan --scope src/       # Scan specific directory
/security-scan --quick            # Fast scan (critical issues only)
/security-scan --focus injection  # Focus on specific category

What This Skill Does

Analyzes code for security vulnerabilities across multiple categories:

1. OWASP Top 10 - Industry-standard web vulnerability categories 2. Secrets Detection - Hardcoded credentials, API keys, tokens 3. Injection Flaws - SQL, XSS, command injection patterns 4. Cryptographic Issues - Weak algorithms, insecure implementations 5. Configuration Problems - Insecure defaults, misconfigurations

Scan Modes

Full Scan (Default)

Comprehensive analysis of all security categories.

/security-scan

Checks performed:

  • All OWASP Top 10 categories
  • Secrets and credential detection
  • Dependency vulnerabilities (if package files exist)
  • Configuration file review

Duration: 2-5 minutes depending on codebase size

Quick Scan

Fast check for critical and high-severity issues only.

/security-scan --quick

Checks performed:

  • Critical injection patterns
  • Exposed secrets
  • Known dangerous functions

Duration: Under 1 minute

Focused Scan

Target specific vulnerability category.

/security-scan --focus <category>

Categories:

  • injection - SQL, XSS, command injection
  • secrets - Credentials, API keys, tokens
  • crypto - Cryptographic weaknesses
  • auth - Authentication/authorization issues
  • config - Configuration security

Output Format

Severity Levels

LevelIconMeaningAction Required
CRITICAL[!]Exploitable vulnerabilityImmediate fix
HIGH[H]Serious security riskFix before deploy
MEDIUM[M]Potential vulnerabilityPlan to address
LOW[L]Minor issue or hardeningConsider fixing
INFO[i]Informational findingAwareness only

Finding Format

[SEVERITY] CATEGORY: Brief description
  File: path/to/file.ext:line
  Pattern: What was detected
  Risk: Why this is dangerous
  Fix: How to remediate

Summary Report

SECURITY SCAN RESULTS
=====================

Scope: src/
Files scanned: 127
Duration: 45 seconds

FINDINGS BY SEVERITY
  Critical: 2
  High: 5
  Medium: 12
  Low: 8

TOP ISSUES
1. [!] SQL Injection in src/api/users.ts:45
2. [!] Hardcoded AWS key in src/config.ts:12
3. [H] XSS vulnerability in src/components/Comment.tsx:89
...

Run `/security-scan --details` for full report.

OWASP Top 10 Coverage

#CategoryDetection Approach
A01Broken Access ControlAuthorization pattern analysis
A02Cryptographic FailuresWeak crypto detection
A03InjectionPattern matching + data flow
A04Insecure DesignSecurity control gaps
A05Security MisconfigurationConfig file analysis
A06Vulnerable ComponentsDependency scanning
A07Auth FailuresAuth pattern review
A08Data Integrity FailuresDeserialization checks
A09Logging FailuresAudit log analysis
A10SSRFRequest pattern detection

See references/owasp/ for detailed detection rules per category.

Detection Patterns

Injection Detection

SQL Injection:

- String concatenation in queries
- Unsanitized user input in database calls
- Dynamic query construction

Cross-Site Scripting (XSS):

- innerHTML assignments with user data
- document.write() with dynamic content
- Unescaped template interpolation

Command Injection:

- exec(), system(), popen() with user input
- Shell command string construction
- Unsanitized subprocess arguments

See references/patterns/ for language-specific patterns.

Secrets Detection

High-Confidence Patterns:

AWS Access Key:     AKIA[0-9A-Z]{16}
AWS Secret Key:     [A-Za-z0-9/+=]{40}
GitHub Token:       gh[pousr]_[A-Za-z0-9]{36,}
Stripe Key:         sk_live_[A-Za-z0-9]{24,}
Private Key:        -----BEGIN (RSA |EC )?PRIVATE KEY-----

Medium-Confidence Patterns:

Generic API Key:    api[_-]?key.*[=:]\s*['"][a-zA-Z0-9]{16,}
Password in Code:   password\s*[=:]\s*['"][^'"]+['"]
Connection String:  (mysql|postgres|mongodb)://[^:]+:[^@]+@

Cryptographic Weaknesses

Weak Algorithms:

- MD5 for password hashing
- SHA1 for security purposes
- DES/3DES encryption
- RC4 stream cipher

Implementation Issues:

- Hardcoded encryption keys
- Weak random number generation
- Missing salt in password hashing
- ECB mode encryption

Integration with Other Skills

With /secrets-scan

Focused deep-dive on credential detection:

/secrets-scan              # Dedicated secrets analysis
/secrets-scan --entropy    # High-entropy string detection

With /dependency-scan

Package vulnerability analysis:

/dependency-scan           # Check all dependencies
/dependency-scan --fix     # Auto-fix where possible

With /config-scan

Infrastructure and configuration review:

/config-scan               # All config files
/config-scan --docker      # Container security
/config-scan --iac         # Infrastructure as Code

Scan Execution Protocol

Phase 1: Discovery

1. Identify project type (languages, frameworks)
2. Locate relevant files (source, config, dependencies)
3. Determine applicable security rules

Phase 2: Static Analysis

1. Pattern matching for known vulnerabilities
2. Data flow analysis for injection paths
3. Configuration review

Phase 3: Secrets Scanning

1. High-confidence pattern matching
2. Entropy analysis for potential secrets
3. Git history check (optional)

Phase 4: Dependency Analysis

1. Parse package manifests
2. Check against vulnerability databases
3. Identify outdated packages

Phase 5: Reporting

1. Deduplicate findings
2. Assign severity scores
3. Generate actionable report
4. Provide remediation guidance

Configuration

Project-Level Config

Create .security-scan.yaml in project root:

# Scan configuration
scan:
  exclude:
    - "node_modules/**"
    - "vendor/**"
    - "**/*.test.ts"
    - "**/__mocks__/**"

# Severity thresholds
thresholds:
  fail_on: critical    # critical, high, medium, low
  warn_on: medium

# Category toggles
categories:
  injection: true
  secrets: true
  crypto: true
  auth: true
  config: true
  dependencies: true

# Custom patterns
patterns:
  secrets:
    - name: "Internal API Key"
      pattern: "INTERNAL_[A-Z]{3}_KEY_[a-zA-Z0-9]{32}"
      severity: high

Ignore Patterns

Create .security-scan-ignore for false positives:

# Ignore specific files
src/test/fixtures/mock-credentials.ts

# Ignore specific lines (use inline comment)
# security-scan-ignore: test fixture
const mockApiKey = "sk_test_fake123";

Command Reference

CommandDescription
/security-scanFull security scan
/security-scan --quickCritical issues only
/security-scan --scope <path>Scan specific path
/security-scan --focus <cat>Single category
/security-scan --detailsVerbose output
/security-scan --jsonJSON output
/security-scan --fixAuto-fix where possible

Related Skills

  • /secrets-scan - Deep secrets detection
  • /dependency-scan - Package vulnerability analysis
  • /config-scan - Configuration security review
  • /review-code - General code review (includes security)

References

  • references/owasp/ - OWASP Top 10 detection details
  • references/patterns/ - Language-specific vulnerability patterns
  • references/remediation/ - Fix guidance by vulnerability type
  • assets/severity-matrix.md - Severity scoring criteria

Related skills

FAQ

What does security-scan check?

security-scan runs structured scans on codebases and configs before release, surfacing dependency vulnerabilities, insecure defaults, exposed secrets patterns, and compliance gaps with severity-ranked remediation guidance for developers.

When should developers run security-scan?

Developers should invoke security-scan before shipping release candidates, when inheriting unfamiliar repositories, or when audit stakeholders request documented vulnerability and misconfiguration review across the project tree.

Securityauditappseccompliance

This week in AI coding

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

unsubscribe anytime.