vigolium-audit

Automate repository security audits with mode-based vulnerability analysis and JSON output.

965|142|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/vigolium/vigolium --skill vigolium-audit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vigolium-audit
Source: https://github.com/vigolium/vigolium/tree/main/platform/vigolium-audit/skills/vigolium-audit
Command: npx skills add https://github.com/vigolium/vigolium --skill vigolium-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you find exploitable security issues in a repository and turn noisy analysis into a structured, confidence-improving findings tree without manually coordinating a complex audit workflow.

Core Features & Use Cases

  • Autonomous multi-agent audit pipeline: Runs a fixed methodology (intel → SAST → adversarial review → PoC → report) to reduce false positives.
  • Mode-based depth control: Supports lite/balanced/deep plus follow-ups like revisit, reinvest, confirm, diff, merge, and longshot to match your intent and constraints.
  • Resume and machine-readable outputs: Continues interrupted runs and emits structured JSON (NDJSON streams) for automation.

Example use case: You need to assess a newly deployed service for critical and high-impact vulnerabilities and want a prioritized, finalized report with PoCs and a stable findings structure.

Quick Start

Run a full deep audit with Claude against your repository by executing: vigolium-audit run --mode deep --agent claude --target /path/to/repo.

Frequently Asked Questions about vigolium-audit

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

FAQPage Schema
How do I automate security audits to reduce false positives in my codebase?▼

To automate a security audit, run a multi-agent pipeline executing intel, SAST, adversarial review, and PoC generation to produce structured findings with reduced false positives. This workflow autonomously triages your codebase and outputs a finalized report without manual coordination.

Can I get JSON output from a codebase vulnerability assessment for CI/CD automation?▼

Yes, you can get JSON output from a codebase vulnerability assessment by using the optional --json flag to emit NDJSON streams. This machine-readable format allows direct integration of finalized security findings and PoC data into CI/CD pipelines.

What is the best way to resume an interrupted codebase vulnerability audit?▼

The best way to resume an interrupted codebase vulnerability audit is to use the revisit or reinvest modes. These modes continue interrupted runs, allowing the multi-agent pipeline to pick up where it left off and finalize structured findings without losing prior analysis.

How does multi-agent SAST triage work for discovering exploitable vulnerabilities?▼

Multi-agent SAST triage works by passing static analysis results through adversarial review and PoC generation to validate exploitable vulnerabilities. This sequential pipeline filters out false positives and produces a stable findings tree with confirmed security issues.

Does the vigolium-audit tool require Claude Code to run a deep security audit?▼

Yes, vigolium-audit requires compatible Claude Code or Codex tooling installed on your PATH to run a deep security audit. You must install the vigolium-audit binary and invoke it with the correct mode, agent, and target parameters to execute the pipeline.

When should I use lite versus deep mode for repository security analysis?▼

Use lite mode for faster repository security analysis and deep mode for thorough assessments. Deep mode runs the full intel-to-reporting pipeline for critical vulnerabilities, while lite mode matches time constraints when you need a quicker codebase triage.