security-audit

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manual security reviews of large codebases miss attack classes, duplicate effort, and report unverified findings. This Skill runs a structured, coverage-led vulnerability hunt that assigns attack classes to focused agents, tracks every unit in a ledger, and only reports findings backed by source evidence and bounded local validation. ## Core Features & Use Cases - Coverage-led hunting waves: Splits a codebase into ledger units mapped to attack classes (injection, access control, memory safety, AI/LLM, cloud, client-side, supply chain, 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/LLM agent targets, each with core disciplines and validation rules. - Strict finding validation: Distinguishes confirmed findings (full source trace plus bounded local proof) from needs_validation candidates, and uses coverage-critic waves to detect gaps before declaring completion. - Use Case: Point it at a multi-tenant SaaS repository; it maps trust boundaries, assigns hunters per subsystem, validates candidates in a sandbox, and produces a deduplicated findings report with 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 attack-class coverage units to hunter agents, validates candidates locally, and returns a deduplicated findings report with severity and remediation.

What vulnerability classes does this security audit cover?

It covers injection, access control, cryptography, business logic, memory safety, client-side XSS and XS-Leaks, cloud/IAM misconfiguration, supply chain, data isolation, desktop IPC, and AI/LLM-specific classes like prompt injection and confused-deputy tool use.

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, dummy data, and strict resource limits. Facts requiring live deployment observation are marked needs_validation with an owner-observed check.

How does the audit avoid false positives in findings?

Every confirmed finding requires a complete source trace, a bounded local observed result, and evidence that no existing control prevents it. Candidates missing a decisive fact are reported as needs_validation without severity, never as confirmed.

Can it audit AI agents, RAG pipelines, and MCP servers?

Yes. A dedicated AI/LLM companion covers indirect prompt injection, memory poisoning, tool-argument injection, confused-deputy authority, action-binding failures, and MCP identity confusion, each with explicit validation rules.

What are the limitations of an automated source-code security audit?

It cannot observe deployment-only facts like live IAM attachments, CDN behavior, or browser header configuration, so those become needs_validation items. Budget or quick-profile runs may defer lower-priority coverage units, which are disclosed in the report.