security-audit

Identify and report security issues across frontend, backend, and deployment pipelines.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/120ventures/claude-skills --skill security-audit-120ventures
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-audit
Source: https://github.com/120ventures/claude-skills/tree/main/security-audit
Command: npx skills add https://github.com/120ventures/claude-skills --skill security-audit-120ventures

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Security gaps in codebases lead to data leaks and compromised apps. This skill provides automated checks to identify and report such risks early.

Core Features & Use Cases

  • Detect hardcoded secrets, missing RLS configurations, and unsanitized inputs
  • Validate authorization and access controls across frontend and backend
  • Generate a structured, actionable security report with remediation guidance

Quick Start

Run the security audit against your repository to surface issues and recommended fixes.

Frequently Asked Questions about security-audit

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

FAQPage Schema
How do I scan my codebase for security vulnerabilities and hardcoded secrets?

To scan your codebase for security vulnerabilities, you run an automated audit against your repository to detect hardcoded secrets, missing RLS, unvalidated inputs, and XSS risks. This process generates a structured report with actionable remediation guidance.

What is Row Level Security and when do I need to audit it in my database?

Row Level Security (RLS) restricts data access at the database level. You need to audit RLS when validating authorization and access controls across your backend, ensuring missing configurations do not lead to unauthorized data exposure.

How do I check for XSS risks and unvalidated inputs in my frontend code?

You check for XSS risks and unvalidated inputs by applying an automated security audit across your frontend code. This identifies unsanitized inputs and generates actionable remediation guidance to fix the vulnerabilities.

Does a codebase security audit work across both frontend and backend deployment pipelines?

Yes, a codebase security audit works across frontend, backend, and deployment pipelines. It validates authorization, access controls, and scans for hardcoded secrets to provide comprehensive coverage.

What is the best way to identify improper access controls in a repository?

The best way to identify improper access controls is running an automated security audit that validates authorization across your frontend and backend. It enforces a structured report aligned with 13 checks to surface issues fast.