Railguard Orchestrated Security Scanner — Enhanced Variant

Coordinate 12 specialized subagents to analyze repository code for security vulnerabilities.

76|9|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/Netflix-Skunkworks/railguard-skill --skill railguard-orchestrated-security-scanner-enhanced-variant
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Railguard Orchestrated Security Scanner — Enhanced Variant
Source: https://github.com/Netflix-Skunkworks/railguard-skill/tree/main/.claude/skills/railguard-orchestrated-scan
Command: npx skills add https://github.com/Netflix-Skunkworks/railguard-skill --skill railguard-orchestrated-security-scanner-enhanced-variant

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill orchestrates a multi-agent security analysis workflow, coordinating 12 specialized subagents to perform Phase 3 vulnerability analysis and consolidate results for FP validation.

Core Features & Use Cases

  • Orchestrates Phase 3 vulnerability analysis across 12 domain-specific agents
  • Maintains per-agent context isolation and gate-dispatch logic
  • Forges a streamlined pipeline from discovery to FP validation with summarized outputs
  • Integrates with LSP/ast-grep tooling to support code analysis workflows

Quick Start

Run this skill against a repository to orchestrate phase 3 vulnerability analysis using 12 specialized subagents.

Frequently Asked Questions about Railguard Orchestrated Security Scanner — Enhanced Variant

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

FAQPage Schema
How do I orchestrate multi-agent security analysis for repository code?

Vulnerability analysis is coordinated across 12 specialized subagents that each load relevant rule files and analyze repository code with per-domain context isolation, merging findings for FP validation.

How does per-domain context isolation work for security vulnerability scanning?

Per-domain context isolation works by loading only relevant rule files into each of the 12 specialized subagents, ensuring security vulnerability scanning remains focused before the orchestrator merges findings.

Can I use LSP and ast-grep for prompt-injection vulnerability analysis?

Yes, LSP and ast-grep tooling integrate with the multi-agent security analysis workflow to support repository code analysis for prompt-injection and other security vulnerabilities.

What is the best way to automate false positive validation after vulnerability discovery?

Automated false positive validation is achieved by passing merged vulnerability findings from the 12 specialized subagents directly to the FP validation pipeline, streamlining the workflow from discovery to summarized outputs.

Does coordinated vulnerability analysis require specialized subagents for different code domains?

Yes, coordinated vulnerability analysis requires 12 specialized subagents to apply domain-specific rules, ensuring each code domain is scanned with relevant context isolation before results are merged.