scan-sec

Scan scoped repository files for security vulnerabilities using 21 rule categories.

48|18|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/pageel/para-workspace --skill scan-sec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scan-sec
Source: https://github.com/pageel/para-workspace/tree/main/templates/common/agents/skills/scan-sec
Command: npx skills add https://github.com/pageel/para-workspace --skill scan-sec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, bash, gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

It helps you detect security vulnerabilities in a repository before you ship by turning a “scan the code” request into a structured, evidence-based report with clear severities.

Core Features & Use Cases

  • Guided security auditing: Checks code for the 21 governed vulnerability categories using reasoning that traces data flow (L1–L4) instead of naive pattern matching.
  • Small vs Large scan modes: Handles small repos inline and large repos via sequential chunking for portability with equivalent output.
  • Bilingual outputs (vi/en): Produces reports in Vietnamese or English depending on your requested language.
  • Optional blast-radius analysis: When enabled, it can add call-tree context to prioritize what to fix first.

Quick Start

Ask the agent to scan security for your repo and generate a report in the language you prefer.

Frequently Asked Questions about scan-sec

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

FAQPage Schema
How does data-flow analysis improve code security scanning compared to pattern matching?

Data-flow analysis improves code security scanning by tracing variable states across L1–L4 execution paths to identify actual vulnerabilities, avoiding the false positives typical of naive pattern matching. It evaluates 21 rule categories to produce evidence-based findings.

Can I run a security vulnerability scan on only staged or uncommitted git changes?

Yes, you can run a security vulnerability scan on scoped git targets like staged, uncommitted, or specific commit windows. This targets only the modified code to produce structured reports faster without analyzing the entire repository.

How do I generate a JSON summary report for vulnerability detection automation?

To generate a JSON summary for vulnerability detection automation, run a repository security scan. The process outputs a canonical JSON file containing structured findings mapped to rule categories, suitable for downstream CI/CD pipelines.

Does this code audit tool require Node and bash to function?

Yes, this code audit tool requires Node, bash, and gh (GitHub CLI) to be installed. These dependencies are necessary to execute the scanning scripts and interact with repository metadata for security analysis.

What is the best way to handle vulnerability detection for large repositories?

The best way to handle vulnerability detection for large repositories is using sequential chunking. This method processes scoped files sequentially, ensuring portability and equivalent output quality without overwhelming system resources.

Why do I need blast-radius analysis in my repository security report?

Blast-radius analysis in a repository security report adds call-tree context to identified vulnerabilities. This helps prioritize which security flaws to fix first by showing the potential impact and reach of the vulnerable code.