security-review

Detect repository signals, run OWASP Dependency-Check and ZAP scanners, and produce a unified security report with a gate decision.

4|1|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/jankneumann/agentic-coding-tools --skill security-review-jankneumann
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-review
Source: https://github.com/jankneumann/agentic-coding-tools/tree/main/.agents/skills/security-review
Command: npx skills add https://github.com/jankneumann/agentic-coding-tools --skill security-review-jankneumann

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill automates an end-to-end security review across repositories by detecting project signals, running scanners (OWASP Dependency-Check and ZAP), normalizing findings, and applying a deterministic risk gate to produce a unified report.

Core Features & Use Cases

  • Profile-driven scanning: detects Python/Node/Java profiles or mixed environments to tailor the scan suite.
  • End-to-end orchestration: coordinates dependency checks and DAST scans, aggregates results, and enforces gating.
  • Output artifacts: emits a machine-readable aggregate JSON, a gate JSON, and a human-friendly Markdown report, with optional OpenSpec integration.

Quick Start

Run the security-review skill on your repository to generate a security report and gate decision.

Frequently Asked Questions about security-review

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

FAQPage Schema
How do I automate security scanning for Python, Node, and Java repositories in CI-CD?

Automated security scanning detects Python, Node, or Java project profiles to tailor the scan suite, coordinating dependency checks and DAST scans. It orchestrates scanners across multiple repositories to aggregate findings and enforce a deterministic risk gate for CI-CD pipelines.

What is the best way to gate CI-CD pipelines using normalized vulnerability findings?

Gating CI-CD pipelines using normalized vulnerability findings requires aggregating scanner outputs into a deterministic risk gate. This process normalizes dependency-check and DAST results, producing a gate JSON artifact that decides whether the security review passes or fails.

Can I generate a machine-readable security gate decision alongside a human-friendly Markdown report?

Generating a security gate decision alongside human-friendly reports produces an aggregate JSON, a gate JSON, and a Markdown report. This normalizes vulnerability findings from multiple scanners into unified output artifacts for both automated pipelines and human review.

Does this security review tool support OpenSpec integration for multi-repository scanning?

This security review tool supports OpenSpec integration, coordinating profile detection, scanner planning, and report rendering across multiple repositories. It detects repository signals and orchestrates scans to satisfy OpenSpec artifact requirements.

Why do I need profile detection before running DAST scans and dependency checks?

Profile detection is required before running DAST scans and dependency checks to identify Python, Node, or Java environments. Detecting these project signals tailors the scan suite, ensuring the appropriate security scanners are planned and executed for accurate vulnerability normalization.