security-scan

Analyze whole-codebase data flows for OWASP Top 10 vulnerabilities.

13|3|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/phrazzld/agent-skills --skill security-scan-phrazzld
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-scan
Source: https://github.com/phrazzld/agent-skills/tree/main/core/security-scan
Command: npx skills add https://github.com/phrazzld/agent-skills --skill security-scan-phrazzld

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pnpm, npm, pip-audit, safety, govulncheck, cargo, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of identifying complex, cross-file security vulnerabilities that traditional file-by-file scanners often miss, ensuring a more comprehensive security posture.

Core Features & Use Cases

  • Whole-codebase analysis: Loads the entire project into a large context window for end-to-end vulnerability tracing.
  • OWASP Top 10 coverage: Analyzes for common and critical web application security risks.
  • Cross-module data flow tracing: Identifies vulnerabilities that span multiple files and modules.
  • Dependency auditing: Scans project dependencies for known vulnerabilities.
  • Secrets scanning: Detects hardcoded secrets and sensitive information.
  • Use Case: Before deploying a new feature, run this Skill to perform a deep security audit, ensuring that no logic flaws, access control issues, or injection vulnerabilities are present across the entire application.

Quick Start

Run a comprehensive security scan on the current project, focusing on authentication and API routes.

Frequently Asked Questions about security-scan

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

FAQPage Schema
How do I scan my codebase for cross-module security vulnerabilities?

A whole-codebase security scan analyzes the entire project by loading it into a large context window to trace end-to-end data flows. This approach identifies complex security risks spanning multiple files and modules that traditional file-by-file scanners often miss.

Does this security analysis cover the OWASP Top 10 and dependency audits?

Yes, this security analysis covers the OWASP Top 10, performs dependency audits using tools like pip-audit and cargo, and scans for hardcoded secrets. It provides comprehensive vulnerability detection for regular security reviews and pre-deployment checks.

What's the best way to detect hardcoded secrets in my source code?

The best way to detect hardcoded secrets is to perform a comprehensive secrets scan across the whole codebase. This process identifies sensitive information and hardcoded credentials embedded within your project files during a deep security analysis.

Can I use pip-audit and cargo for dependency vulnerability checks?

Yes, you can use pip-audit and cargo alongside other dependency managers like npm and pnpm. The analysis integrates these tools to perform dependency audits, scanning your project dependencies for known vulnerabilities and ensuring a secure software supply chain.

Why does whole-codebase vulnerability analysis find risks that file-by-file scanners miss?

Whole-codebase vulnerability analysis finds missed risks because it uses a large context window to trace cross-module data flows. By evaluating the entire project simultaneously, it detects logic flaws and injection vulnerabilities that isolated file-by-file scanning cannot track.