vibe-security

Audit codebases for security vulnerabilities with prioritized fixes.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/Seva-Eats/seva-web --skill vibe-security-seva-eats
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibe-security
Source: https://github.com/Seva-Eats/seva-web/tree/main/.agents/skills/vibe-security
Command: npx skills add https://github.com/Seva-Eats/seva-web --skill vibe-security-seva-eats

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you audit a codebase for security issues that AI-generated and rapidly built applications often miss, including exposed secrets, broken authorization, insecure payments, and unsafe trust in client-side data.

Core Features & Use Cases

  • Secrets and environment checks: Detect hardcoded credentials, leaked keys, and unsafe client-side environment variables before they reach production.
  • Access control and auth review: Review authentication flows, middleware, server actions, route handlers, and database permissions for bypasses and missing checks.
  • Payments and abuse prevention: Spot client-controlled pricing, weak webhook validation, and missing rate limits that can lead to fraud or cost spikes.
  • Example use case: Use this Skill when reviewing a Next.js, Supabase, Firebase, or mobile app to identify exploitable issues and turn them into concrete fixes.

Quick Start

Ask the skill to audit the repository for security vulnerabilities and prioritize the most exploitable findings with clear remediation steps.

Frequently Asked Questions about vibe-security

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

FAQPage Schema
How do I audit a Supabase codebase for security vulnerabilities introduced by AI?

To audit a Supabase codebase for security vulnerabilities, systematically inspect repository files for exposed secrets, broken authentication, and missing RLS database access controls. This process prioritizes exploitable findings and provides concrete before-and-after fixes for each issue.

What security flaws are most commonly missed in rapidly built web applications?

Rapidly built web applications most commonly miss exposed secrets, unsafe client-side environment variables, broken authorization bypasses in middleware, and client-controlled pricing in payment flows. These security flaws stem from unsafe trust in client-side data and missing server-side validation.

Does this security audit review Next.js server actions and route handlers?

Yes, this security audit evaluates Next.js server actions and route handlers. It systematically inspects authentication flows, middleware, and database permissions within these components to identify missing access control checks and exploitable authorization bypasses.

How do I check my payment integration for client-controlled pricing and webhook validation?

To check payment integrations for client-controlled pricing and webhook validation, audit the codebase for weak webhook validation signatures, missing rate limits, and client-side price manipulation. This identifies fraud risks and prevents unexpected cost spikes.

Can I scan mobile app bundles for exposed environment variables and deployment issues?

Yes, you can scan mobile app bundles for exposed environment variables and insecure deployment settings. The security audit inspects mobile project repositories to detect hardcoded credentials, leaked keys, and unsafe trust in client-side data before production launch.