vibe-security

Audit code for security vulnerabilities in AI-generated applications.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/Maitreya04/pasplmaster --skill vibe-security-maitreya04
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibe-security
Source: https://github.com/Maitreya04/pasplmaster/tree/main/.cursor/skills/vibe-security
Command: npx skills add https://github.com/Maitreya04/pasplmaster --skill vibe-security-maitreya04

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill audits codebases to identify and remediate common security vulnerabilities introduced by AI-generated code in vibe-coded applications, helping teams prevent data leaks, insecure configurations, and misused credentials.

Core Features & Use Cases

  • Secrets & Environment Variables: Scan for hardcoded keys, client-side exposure, and missing .gitignore coverage; verify environment handling follows best practices.
  • Access Control & Authentication: Review RBAC/RLS, auth flows, middleware protection, and server actions/route handlers for proper authentication and authorization.
  • Data Validation & Input Handling: Check input validation, SQL/ORM safety, and defense against injection or mass assignment.
  • Deployment & Data Security: Verify environment separation, security headers, and production-ready deployment configurations.
  • Use Case: When reviewing a vibe-coded project that handles user data, secrets, and payments, the skill will flag insecure patterns and propose concrete fixes.

Quick Start

Provide a comprehensive security review of my vibe-coded project and return a prioritized remediation plan.

Frequently Asked Questions about vibe-security

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

FAQPage Schema
How do I audit AI-generated code for security vulnerabilities?

To audit AI-generated code for security vulnerabilities, scan for hardcoded API keys, broken access control, misconfigurations, and insecure data flows. This review produces actionable findings with risk ratings and concrete remediation steps.

What security blind spots are common in vibe-coded apps?

Common security blind spots in vibe-coded apps include exposed environment variables, missing .gitignore coverage, improper authentication in server actions, injection risks, and insecure production deployment configurations.

How do I check my codebase for exposed API keys and environment variables?

Check for exposed API keys and environment variables by scanning for hardcoded secrets, verifying client-side exposure, and ensuring .gitignore coverage. Confirm that environment handling follows secure separation and best practices.

Can I review authentication and access control in AI-generated code?

You can review authentication and access control in AI-generated code by evaluating RBAC and RLS configurations, auth flows, and middleware protection across server actions and route handlers to verify proper authorization.

What is the best way to validate input and prevent injection in vibe-coded projects?

The best way to validate input and prevent injection in vibe-coded projects is to check input validation mechanisms, verify ORM safety, and ensure proper defense against mass assignment and SQL injection vulnerabilities.

Does this security audit verify deployment and data security configurations?

This security audit verifies deployment and data security configurations by checking environment separation, validating security headers, and reviewing production-ready deployment settings to prevent insecure data flows.