security

Scans codebases for vulnerabilities using a three-pass security review architecture.

1|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/vickysrawat/AI-Assisted-development --skill security-vickysrawat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security
Source: https://github.com/vickysrawat/AI-Assisted-development/tree/main/skills/security
Command: npx skills add https://github.com/vickysrawat/AI-Assisted-development --skill security-vickysrawat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Security issues like injection flaws, broken access control, exposed secrets, and cloud misconfigurations are easy to miss in manual code review, especially across polyglot stacks. This Skill runs a structured, repeatable security review that detects the project's language stack, applies deterministic vulnerability patterns, layers expert persona analysis, and produces a fingerprinted findings ledger plus an HTML report. ## Core Features & Use Cases - Three-pass scan architecture: Pass 1 applies deterministic rule-based patterns (injection, auth, IDOR, secrets, SSRF, XXE, misconfiguration); Pass 2 runs four focused persona reviews (Attacker, Data Protection, Access Control, Infrastructure); Pass 3 performs an open-ended adversarial analysis for business-logic and interaction flaws. - Stack-aware and scoped scanning: Detects .NET, TypeScript/Angular, Python, Java, Go, and VSTO projects, loads only matching language references, and supports scope flags like --changed, --pr, --full, --ci, and --area, with cache-aware incremental scans. - Compliance and reporting: Maps findings to SOC2, ISO 27001, NIST CSF, PCI-DSS, and HIPAA controls, generates a self-contained HTML report, maintains a reconciled security ledger, and can produce weekly security health summaries for managers. - Use Case: Before merging a pull request in an Angular + ASP.NET Core application, run a security review with --pr to catch a missing [Authorize] attribute, an IDOR in a controller route, and a secrets file not covered by .gitignore, then track the findings to closure in the security ledger. ## Quick Start Ask the assistant to run a security review of this repository for vulnerabilities and generate the findings report.

Frequently Asked Questions about security

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

FAQPage Schema
How do I run a security review on my codebase?

Invoke the security review skill with an optional scope flag such as --changed, --pr, --full, or --ci. Without a flag in an interactive session it presents a scope menu; in CI it defaults to a cache-aware full scan of the repository.

What vulnerabilities does a three-pass security scan detect?

Pass 1 detects injection, broken authentication, IDOR, secrets in code, weak crypto, misconfiguration, SSRF, XXE, and insecure deserialization. Pass 2 personas catch exploitation chains, data-flow leaks, and authorization gaps, while Pass 3 finds business-logic and interaction flaws.

Does the security scan support .NET, Angular, Python, and Java projects?

Yes, the skill detects the project's language stack before scanning and loads only matching language-specific patterns. It covers .NET Framework through modern ASP.NET, Angular and React, Python, Java, Go, plus VSTO add-ins and cloud IaC files.

Can I map security findings to SOC2 or HIPAA compliance controls?

Yes, loading the compliance-controls reference maps findings to SOC2 TSC, ISO 27001:2022, NIST CSF 2.0, PCI-DSS v4, and HIPAA Security Rule controls. Mention the framework when requesting the review to activate compliance mapping.

How does incremental scanning avoid re-reviewing unchanged files?

The skill maintains a file cache recording character counts and last-scanned timestamps, skipping unchanged files on default scans. Use --full or --ci to bypass the cache, or --changed and --pr to scan only git-modified files.

Why are some Pass 3 findings labeled as hypotheses rather than vulnerabilities?

Pass 3 produces advisory, LLM-inferred risk hypotheses that are not fingerprinted or entered into the security ledger. They flag possible interaction or logic flaws that require manual validation before being treated as confirmed vulnerabilities.