sc3-vuln-scan

Orchestrate vulnerability scanners to produce a unified vulnerabilities.md report.

Updated Jun 23, 2024
One-click install
npx skills add https://github.com/n4igme/randscript --skill sc3-vuln-scan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sc3-vuln-scan
Source: https://github.com/n4igme/randscript/tree/main/llm/skills/scode/sc3-vuln-scan
Command: npx skills add https://github.com/n4igme/randscript --skill sc3-vuln-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the coordination of vulnerability scanners to generate a unified vulnerabilities.md report.

Core Features & Use Cases

  • Orchestrates sub-skanners 3a–3m, 3w-*, and 3x-a–3x-c in a defined sequence to cover common attack surfaces.
  • Aggregates findings into a single vulnerabilities.md with standardized severity, confidence, and provenance metadata.
  • Supports idempotent reruns and structured outputs to feed sc4-validate and automated reporting.

Quick Start

Run all vulnerability sub-skanners in order to produce a consolidated vulnerabilities.md report.

Frequently Asked Questions about sc3-vuln-scan

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

FAQPage Schema
How do I orchestrate multiple vulnerability scanners to generate a unified report?

To orchestrate vulnerability scanners and generate a unified report, this Skill coordinates sub-skanners in a defined sequence and aggregates findings into a single vulnerabilities.md file with standardized severity and provenance metadata.

Can I automate bug bounty workflows across web, API, web3, and systems scanners?

Yes, you can automate bug bounty workflows across traditional web/API, web3, and systems scanners. The orchestration sequence coordinates multiple sub-scanners to aggregate findings into a consolidated vulnerabilities.md report.

What is the output format for aggregated vulnerability findings?

The output format for aggregated vulnerability findings is a unified vulnerabilities.md file. It enforces a fixed structure for sub-scan outputs and includes standardized severity, confidence, and provenance metadata for each finding.

Does the vulnerability scan orchestration support idempotent reruns?

Yes, the vulnerability scan orchestration supports idempotent reruns. This allows you to safely execute the coordinated sub-scanners multiple times without duplicating findings, ensuring structured outputs remain stable for downstream validation.

How do I ensure my vulnerability findings feed directly into automated validation and reporting?

To ensure vulnerability findings feed into automated validation, the orchestration outputs structured findings with standardized metadata into vulnerabilities.md. This standardized format is designed to directly feed sc4-validate and downstream automated reporting workflows.

Are there limitations when coordinating vulnerability sub-scanners for different attack surfaces?

A key limitation is that the orchestration relies on a fixed structure for sub-scan outputs and requires an assessment/vulnerabilities.md file. It coordinates specific defined sub-scanners in a set order rather than supporting arbitrary scanner integrations.