security-audit-deep

Orchestrates multi-agent source-code security audits with coverage ledgers and validated findings.

Updated Sep 17, 2026
One-click install
npx skills add https://github.com/karenrebecag/spec-driven-standards --skill security-audit-deep-karenrebecag
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-audit-deep
Source: https://github.com/karenrebecag/spec-driven-standards/tree/main/plugins/security/skills/security-audit-deep
Command: npx skills add https://github.com/karenrebecag/spec-driven-standards --skill security-audit-deep-karenrebecag

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manual security reviews of large codebases miss entire attack surfaces because reviewers cannot systematically cover every trust boundary, and unvalidated findings waste triage time on false positives. ## Core Features & Use Cases - Coverage-led hunting waves: Decomposes a codebase into deterministic coverage units tracked in a ledger, assigns them to focused hunter agents, and runs coverage-critic passes to detect gaps before declaring completion. - Domain-specific attack classes: Ships companion references for AI/LLM agents, web protocols, client-side browser code, cloud deployment, memory safety, data isolation, desktop/mobile IPC, supply chain, and resource exhaustion. - Rigorous validation gates: Distinguishes confirmed findings (full source trace plus bounded local reproduction in a sandbox) from needs_validation candidates that require owner-observed deployment facts. - Use Case: Point the audit at a multi-tenant SaaS repository; it maps trust boundaries, hunts injection, access-control, and tenant-isolation defects per subsystem, and returns a prioritized report where every finding carries a source trace and reproduction evidence. ## Quick Start Run a deep security audit of this repository and report only source-validated vulnerabilities with their traces and remediation steps.

Frequently Asked Questions about security-audit-deep

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

FAQPage Schema
How do I run a deep security audit on my codebase?

Invoke the audit against your repository root; it builds an architecture map, derives coverage units per trust boundary, and assigns them to hunter agents. Findings come back as structured records with source traces, severity, and remediation guidance.

What vulnerability classes does a source-code security audit cover?

It covers injection, access control, cryptography, business logic, and feature abuse, plus domain-specific classes for AI/LLM agents, browser client-side code, cloud deployment, memory safety, data isolation, and local IPC. Classes are selected per target type during the mapping phase.

How does the audit avoid false positive vulnerability reports?

Every candidate must pass a validation gate requiring a complete source trace and a bounded local reproduction in a sandbox. Findings needing unobservable deployment facts are labeled needs_validation with the exact missing check instead of being reported as confirmed.

Can this audit review AI agents and LLM pipelines for prompt injection?

Yes, a dedicated companion covers RAG retrieval, memory poisoning, tool-argument injection, confused-deputy authority, action-binding failures, and MCP identity confusion. It requires a code-level boundary failure, not persuasive prompt text alone, before reporting.

What are the limitations of automated source-code security review?

Source review cannot confirm facts that only exist at runtime, such as deployed network policy, provider IAM attachments, or browser header behavior. Those items are returned as needs_validation with an owner-observed check rather than confirmed findings.