security-audit

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manual security reviews of large codebases miss attack classes and produce unverified findings. This Skill runs a structured, coverage-led vulnerability hunt that assigns attack classes to focused hunter agents, validates candidates against strict evidence rules, and tracks every reviewed unit in a ledger. ## Core Features & Use Cases - Coverage-led hunting waves: Splits a codebase into deterministic coverage units mapped to attack classes (injection, access control, memory safety, AI/LLM, cloud, client-side, and more) so no boundary is silently skipped. - Domain-specific hunting guides: Ships companion references for web/auth, client-side, cloud deployment, data isolation, desktop/mobile IPC, memory safety, and AI/agent trust boundaries. - Strict validation gates: Distinguishes confirmed findings (source trace plus bounded local proof) from needs_validation candidates, preventing speculative or overstated reports. - Use Case: Point it at a multi-tenant SaaS repository; it maps trust boundaries, dispatches hunters per subsystem, runs coverage critics to find gaps, and returns a deduplicated findings report with fingerprints, traces, and remediation guidance. ## Quick Start Ask the agent to run the security-audit skill against this repository and produce a validated findings report.

Frequently Asked Questions about 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 AI agents?▼

Invoke the security-audit skill against your repository. It maps trust boundaries in an architecture phase, assigns coverage units to hunter agents by attack class, validates candidates with bounded local checks, and returns a structured findings report.

What vulnerability classes does this security audit cover?▼

It covers injection, access control, cryptography, business logic, memory safety, client-side DOM issues, cloud/IAM misconfiguration, data isolation, supply chain, desktop IPC, and AI/LLM-specific classes like prompt injection, memory poisoning, and MCP identity confusion.

Can this skill audit AI agents and LLM applications?▼

Yes. The AI-AND-LLM.md reference covers RAG pipelines, persistent memory poisoning, tool-argument injection, action-binding failures, MCP server identity confusion, and insecure output rendering, with dedicated validation rules for each class.

Does the audit test live or deployed services?▼

No. Validation is restricted to source review and bounded local execution in a sandbox with no external network. Facts requiring deployed infrastructure, provider behavior, or live identity systems are marked needs_validation with an owner-observed check plan.

Why are some findings marked needs_validation instead of confirmed?▼

A finding is confirmed only when source evidence plus a bounded local check proves the full boundary violation. When a deployment, browser, provider, or runtime fact cannot be observed locally, the candidate is recorded as needs_validation with the exact missing fact.