security-audit

Review code, configuration, and service behavior for security risks across trust boundaries and auth controls.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/vesviet/agent-skills --skill security-audit-vesviet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-audit
Source: https://github.com/vesviet/agent-skills/tree/main/core/skills/security-data/security-audit
Command: npx skills add https://github.com/vesviet/agent-skills --skill security-audit-vesviet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security reviews often miss real attack surfaces by focusing on checklists instead of trust boundaries, and AI/ML systems introduce new threat classes that traditional audits do not cover. This Skill provides a structured process for auditing changes, services, and deployments against concrete risk areas with severity-ranked findings. ## Core Features & Use Cases - Trust Boundary Analysis: Identify sensitive data, actors, external inputs, and trusted systems before scoping the audit. - Standards-Based Scoring: Score vulnerabilities with CVSS 4.0 (BTE nomenclature), check OWASP Top 10:2025 (including A10 exceptional conditions), and apply OWASP ASI01–ASI10 controls for agentic AI systems. - Zero Trust Verification: Validate mTLS with SPIFFE/SPIRE workload identity and SLSA Level 3 supply chain integrity for production builds. - Use Case: Before merging a change that adds a new API endpoint, run the audit to verify authentication, input validation, secret handling, and runtime exposure, then receive findings sorted by severity with reproducible evidence. ## Quick Start Use the security-audit skill to review this change for security risks and report findings by severity.

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 a code change?▼

Start by identifying the trust boundary: sensitive data, actors, external inputs, and trusted systems. Then review authentication, input validation, secret handling, and whether new endpoints or background paths bypass existing controls, reporting findings by severity.

What is OWASP ASI and when should I apply it?▼

OWASP ASI is the Top 10 for agentic AI systems, covering threats like prompt injection (ASI01), excessive agency (ASI03), and insecure retrieval (ASI09). Apply all ten controls whenever auditing AI/ML or agent-based systems.

How does CVSS 4.0 scoring work in a security audit?▼

CVSS 4.0 uses BTE nomenclature distinguishing Vulnerable System impacts (VC/VI/VA) from Subsequent System impacts (SC/SI/SA), plus Supplemental metrics like Automatable and Recovery. Scores translate into P0 through P3 severity tiers for prioritization.

Does this audit cover zero trust and mTLS deployments?▼

Yes. Zero Trust Architecture deployments must enforce mTLS between all internal services using SPIFFE/SPIRE for workload identity. Any service-to-service communication without a valid SVID is flagged and blocked.

What are common mistakes when reporting security findings?▼

Common failures include burying high-severity findings in summaries, omitting reproducible evidence, and including real credentials in reports. Every finding needs a path, a command, expected versus actual output, and redacted secrets.

When should I use a focused review versus a full-service risk assessment?▼

Use a focused review for a concrete change, checking new endpoints, event paths, and configuration exposure. Use a full-service assessment when evaluating overall posture, including debug surfaces, runtime permissions, network reachability, and rollback assumptions.