audit-security

Identify security vulnerabilities and data exposure in source code.

6|1|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/ferdiangunawan/rpi-stack --skill audit-security
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-security
Source: https://github.com/ferdiangunawan/rpi-stack/tree/main/audit-security
Command: npx skills add https://github.com/ferdiangunawan/rpi-stack --skill audit-security

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies and reports security vulnerabilities and data exposure in source code to prevent risk escalation during development.

Core Features & Use Cases

  • Background audits during /implement to surface P0 findings early.
  • Standalone /audit-security runs to review a specific feature, file set, or repository.
  • Generates structured findings suitable for injection to the main agent and for post-task reporting.

Quick Start

Audit the specified files or feature for security vulnerabilities and output a structured report to the designated output directory.

Frequently Asked Questions about audit-security

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

FAQPage Schema
How do I run a security audit on my source code to find vulnerabilities?

Run a security audit on source code using a standalone command to scan specific files, features, or the entire codebase. The audit identifies vulnerabilities and data exposure, writing structured findings to an output JSON file and generating a Markdown report.

Can I automatically surface critical security risks during feature implementation?

Yes, you can automatically surface critical security risks during feature implementation by running background security audits. This process identifies P0 findings early and injects them into the main agent for immediate remediation.

What types of security vulnerabilities can a code review background audit detect?

A code review background audit detects security vulnerabilities and data exposure in source code, implementing P0 through P2 checks to identify critical risks and prevent escalation during development.

How are security audit findings reported and formatted for remediation?

Security audit findings are reported as structured JSON output and a feature-specific Markdown report. This structured format supports injecting P0 findings directly into the main agent for immediate remediation alongside post-task reporting.

What is the best way to prevent security risk escalation during development?

The best way to prevent security risk escalation is running background security audits during implementation. This approach continuously identifies and reports vulnerabilities and data exposure, allowing early remediation of P0 findings before risks compound.