security-scan

Automate OWASP Top 10 checks, secret detection, and dependency audits in code.

8|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/ShaheerKhawaja/ProductionOS --skill security-scan-shaheerkhawaja
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-scan
Source: https://github.com/ShaheerKhawaja/ProductionOS/tree/main/.claude/skills/security-scan
Command: npx skills add https://github.com/ShaheerKhawaja/ProductionOS --skill security-scan-shaheerkhawaja

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates security scanning of codebases to detect OWASP Top 10 vulnerabilities, hardcoded secrets, and risky dependencies during development and reviews.

Core Features & Use Cases

  • Auto-activates when sensitive areas such as auth, payment, credentials, or admin files are edited, performing OWASP checks, secret detection, and dependency audits.
  • Continuously verifies authentication/authorization, input validation, and secure coding patterns across code changes.
  • Use Case: When modifying critical security-sensitive modules, the scanner flags vulnerabilities and suggests fixes to reduce risk.

Quick Start

Run the security-scan to audit the current repository for secrets, dependencies, and OWASP risks.

Frequently Asked Questions about security-scan

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

FAQPage Schema
How do I automate OWASP Top 10 checks during code reviews?

Automate OWASP Top 10 checks during code reviews by running a security scan that continuously verifies authentication, input validation, and secure coding patterns across code changes. The scanner flags vulnerabilities and suggests fixes to reduce risk in sensitive modules.

What is the best way to detect hardcoded secrets in a repository?

Detect hardcoded secrets by running an automated security scan on the repository. The scanner auto-activates when sensitive areas like credential files are edited, identifying exposed secrets during development and code reviews.

How do I audit risky dependencies for known CVEs in a web application?

Audit risky dependencies for known CVEs by running an automated dependency audit within the security scanner. It checks web applications and services to detect risky dependencies during development and code reviews.

Can I integrate automated security checks into CI pipelines?

Yes, you can integrate automated security checks into CI pipelines. The scanner applies to web applications, services, and CI pipelines to detect OWASP risks, hardcoded secrets, and known CVEs during development.

Does static analysis work for detecting CSRF protection and parameterized query issues?

Yes, static analysis works for detecting these issues. The security scan enforces automated checks for CSRF protection and parameterized queries by integrating with the repository's file patterns and trigger keywords.