app-security-gate

Audits web apps and APIs against adversarial attack paths before production release.

3|Updated Jul 28, 2026
One-click install
npx skills add https://github.com/marcmarti9/agentit --skill app-security-gate-marcmarti9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: app-security-gate
Source: https://github.com/marcmarti9/agentit/tree/main/skills/app-security-gate
Command: npx skills add https://github.com/marcmarti9/agentit --skill app-security-gate-marcmarti9

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? A working happy path is not evidence that an application is safe to ship. This Skill turns security review into a release gate: it inspects the actual implementation, tests realistic misuse paths like IDOR, injection, and webhook forgery, applies safe fixes, and retests the final tree before declaring PASS or BLOCKED. ## Core Features & Use Cases - Adversarial Release Gate: Produces a definitive PASS or BLOCKED verdict with automatic release blockers for exposed secrets, authorization bypass, injection, and unsafe uploads. - Full Attack-Surface Review: Covers secrets exposure, authentication, authorization and tenant isolation, database mutation, input/output sinks, file uploads, webhooks, deployment hardening, and dependency supply chain. - Stack-Specific Rules: Loads targeted guidance for Supabase, Firebase, Next.js, serverless platforms, Stripe, PostgreSQL/ORMs, object storage, OAuth, and AI/LLM features. - Use Case: After an AI coding agent rapidly builds a SaaS dashboard with Supabase auth and Stripe payments, run this gate before launch to test cross-tenant access, webhook signature verification, and RLS policies, then fix and retest findings. ## Quick Start Ask the agent to run the app security gate on this repository and report whether it is safe to deploy to production.

Frequently Asked Questions about app-security-gate

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

FAQPage Schema
How do I check if my web app is secure before deploying?▼

Run a security gate that maps the real attack surface, tests authentication, authorization, injection, uploads, and webhooks adversarially, then retests after fixes. The result is a PASS or BLOCKED verdict with documented findings and residual risks.

How to test for IDOR and authorization bypass in an API?▼

Test IDOR by requesting another user's records through changed IDs, body fields, or query parameters, and by calling admin actions as a normal user. Client-side checks and hidden routes are never sufficient; server-side ownership and tenant constraints must be verified.

Does this security review work with Supabase and Firebase apps?▼

Yes, stack-specific rules cover Supabase, Firebase, Next.js, managed auth providers, Stripe, PostgreSQL/ORMs, and object storage. It correctly treats publishable client keys as public while testing RLS policies and security rules as the real authorization boundary.

What automatically blocks a production release in a security gate?▼

Release is blocked by exposed privileged secrets, unauthenticated access to protected functionality, authorization bypass, realistic injection or RCE paths, plaintext password storage, unsafe uploads, unverified security-sensitive webhooks, or production debug surfaces.

When should I not use a full pre-deploy security gate?▼

Skip the gate for generic security concept questions, a single isolated vulnerability question, or work with no runnable application surface. Use control-level secure-coding guidance directly for those cases instead.