production deploy gate
A 7-gate security and reliability auditor for production-ready AI-generated code.
$7
Works with the AI Agents you already use
production deploy gate
Example session with this skill installed
Run the 7-Gate Verification Protocol on the current branch before I merge this PR to main. I've added a new user profile update endpoint and a database migration.
- Read your context and instructions
- Compiled the production deploy gate
I have completed the 7-gate security and reliability audit on the current changeset. The check identified a critical authorization flaw in the new profile update route.
🛡️ Production Deployment Readiness Report
- Gate 1 (Secrets & Credentials): PASS — No raw keys found.
.envis correctly ignored in.gitignore. - Gate 2 (SQL Injection): PASS — Migration uses Drizzle ORM's parameterized query builder.
Gate 3 (Auth & IDOR Guard): FAIL — PUT /api/user/:id does not verify req.user.id === resource.owner_id. Any logged-in user can update any profile.
- Gate 4 (CORS & Rate Limiting): PASS — Rate limiting middleware is active on all
/apiroutes.
Gate 5 (Error Handling): PASS — Async controllers are wrapped in try/catch with standardized 400/500 JSON responses.
- Gate 6 (Health Endpoint): PASS —
GET /api/healthreturns status 200. - Gate 7 (Typecheck & Build): PASS —
npm run typecheckexited with code 0.
Verdict: BLOCKED - ACTION REQUIRED
Next steps
- Update
src/routes/user.tsto include an ownership check before executing the database update. - Add a unit test verifying that a 403 Forbidden is returned when user A attempts to update user B's profile.
- Rerun the audit using
node scripts/audit-gate.jsafter the fix.
Connects securely to your tools. The creator never sees your data.
About this skill
Shipping AI-generated code directly to production introduces significant risks, from leaked environment variables to broken authorization logic. This skill enforces a deterministic 7-gate verification protocol to ensure every pull request or deployment meets production-grade standards. It eliminates the guesswork of "vibe-coding" by running a structured audit across security, reliability, and type safety.
What it does
- Secrets detection scans for hardcoded API keys, JWT secrets, and unignored
.envfiles. - Injection prevention audits database queries for raw string concatenation and enforces parameterized queries or ORM sanitizers.
- Authorization verification checks for IDOR/BOLA vulnerabilities by ensuring resource ownership is verified at the database level.
- Resilience testing validates that asynchronous operations include proper error handling and never leak stack traces to the client.
- Infrastructure check verifies CORS configurations, rate limiting policies, and the existence of lightweight health-check endpoints.
How it works
- Initiate audit by requesting a production readiness check on a specific branch or changeset.
- Review the 7-Gate Report which provides a PASS/FAIL status for secrets, SQL, Auth, Rate Limiting, Errors, Health, and Build.
- Execute local scanner using the included
node scripts/audit-gate.jsfor an automated verification pass. - Remediate blocks based on the specific details provided for any failing gate.
Frameworks & tools
Works with any stack using git, but provides specific optimizations for Node.js, TypeScript, Prisma, Drizzle, SQLAlchemy, and standard CI/CD environments.
Why this beats prompting it yourself
Generic prompts often miss subtle authorization flaws like IDOR or forget to check .gitignore hygiene. This skill provides a structured, repeatable framework that ensures no critical security gate is skipped during the pre-deployment rush.
Use cases
- Auditing a feature branch before merging a PR into the main production line.
- Verifying that AI-refactored database queries haven't introduced SQL injection risks.
- Checking new API endpoints for proper ownership verification and rate limiting.
- Ensuring a project is ready for a clean build and deployment without silent runtime crashes.
Known limitations
Requires a manual trigger or script execution to initiate the audit. It cannot automatically block git commits without integration into a pre-commit hook or CI pipeline.
Requires manual invocation or script execution. Cannot block git commits unless integrated into pre-commit hooks. Optimized for Node/TS and common ORMs; custom engines may require manual mapping.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 6 days ago
Requires