void-security-audit

Audits codebases for OWASP Top 10, STRIDE, secrets, and supply-chain vulnerabilities through phase-driven static analysis.

Updated May 29, 2026
One-click install
npx skills add https://github.com/voidcorp-core/void-harness --skill void-security-audit-voidcorp-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: void-security-audit
Source: https://github.com/voidcorp-core/void-harness/tree/main/packages/core/skills/void-security-audit
Command: npx skills add https://github.com/voidcorp-core/void-harness --skill void-security-audit-voidcorp-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Periodic deep security reviews are hard to run consistently: ad-hoc scans miss attack surfaces, produce noisy findings, and blur the line between real exploitable vulnerabilities and theoretical hardening gaps. This Skill provides a structured, read-only, phase-driven audit methodology that maps the full attack surface and reports only high-confidence, exploitable findings. ## Core Features & Use Cases - Phase-driven audit coverage: Fourteen phases spanning secrets archaeology, dependency supply chain, CI/CD pipelines, infrastructure, webhooks, LLM/prompt-injection risks, skill supply chain, OWASP Top 10, STRIDE threat modeling, and data classification. - Scoped and diff modes: Run full, comprehensive, or narrowly scoped audits (infra, code, owasp, supply-chain, skills, or a named domain), optionally constrained to files changed on the current branch. - Zero-noise confidence gating: Every finding must clear a confidence threshold, carry a concrete exploit scenario, and quote the motivating line of code; optional independent verification via a fresh-context agent filters false positives. - Use Case: Before launching a payments feature, invoke a scoped audit on the auth domain to trace webhook signature verification, session handling, and secrets exposure, then receive a severity-ranked findings report with exploit paths and remediations. ## Quick Start Ask the agent to run a full security audit of this repository and produce a severity-ranked findings report with exploit scenarios.

Frequently Asked Questions about void-security-audit

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

FAQPage Schema
How do I run a security audit on my codebase with an AI agent?

Invoke the audit skill and choose a mode: full for a zero-noise deep scan, comprehensive for broader tentative findings, or scoped to focus on one area like infra, code, or supply-chain. The skill traces code statically and produces a severity-ranked findings report with exploit paths.

What does an OWASP Top 10 security audit cover?

It covers broken access control, cryptographic failures, injection, insecure design, misconfiguration, outdated components, auth failures, integrity failures, logging gaps, and SSRF. Each category is checked with targeted grep patterns scoped to the detected stack, with framework-aware false-positive rules.

Can the audit scan only files changed on my current branch?

Yes, diff mode constrains every phase to files and configs changed on the current branch versus the base, and limits git-history secret scans to the branch's commits. It combines with any scope such as infra, code, or a named domain.

Does the security audit make live requests or run scanners?

No, the skill is strictly read-only and static: it traces code and never sends HTTP requests or starts scanners. Live probing is delegated to the separate void-harness security command, which enforces target authorization and reports degraded scans honestly.

How does the audit avoid false positives in security findings?

Findings must pass a confidence gate (8/10 in full mode), include a concrete exploit scenario, and quote the exact file and line. Where available, an independent verifier agent re-scores each finding with fresh context, and verified patterns trigger variant analysis across the codebase.

What are the limitations of an AI-assisted security audit?

It catches common vulnerability patterns but is not comprehensive and can miss subtle vulnerabilities or complex auth flows. For production systems handling payments or PII, it should serve as a first pass between professional penetration tests, not the only line of defense.