security-review

Name: security-review
Availability: InStock
Author: aquarius-wing

Identify and remediate security vulnerabilities in code across authentication and input handling.

Updated Feb 21, 2026

Search Tags:#security #authentication #review #input-validation #api-security #secrets-management #secure-coding

Ready to run

npx skills add https://github.com/aquarius-wing/polymarket-dev-tools --skill security-review-aquarius-wing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security-review
Source: https://github.com/aquarius-wing/polymarket-dev-tools/tree/main/.cursor/skills/security-review
Command: npx skills add https://github.com/aquarius-wing/polymarket-dev-tools --skill security-review-aquarius-wing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Security vulnerabilities are a risk across authentication, input handling, secrets, API endpoints, and payment features. This skill provides a structured approach to identify and remediate those risks early in development.

Core Features & Use Cases

Comprehensive security checklist covering secrets management, input validation, authentication, authorization, rate limiting, and secure coding patterns.
Practical guidance for implementing security controls in API design, data handling, and third-party integrations.
Use Case: Integrate the checklist into code reviews or CI/CD pipelines to prevent common vulnerabilities before deployment.

Quick Start

Review your next code change for security implications and run the security checklist before merging.

Frequently Asked Questions about security-review

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

FAQPage Schema

How do I perform a security review on code changes touching authentication and API endpoints?▼

Code security reviews use a comprehensive checklist to identify and remediate vulnerabilities in authentication, API endpoints, and input handling. You can integrate this checklist into CI/CD pipelines or run it manually before merging code changes.

What is the best way to check for secrets management and input validation issues during a code review?▼

The best way to check for secrets management and input validation issues is applying best-practice patterns and a structured security checklist. This approach catches common vulnerabilities across backend and frontend layers during development or code review.

Can I integrate security checks into CI/CD pipelines for payment features and third-party integrations?▼

Yes, you can integrate security checks into CI/CD pipelines for payment features and third-party integrations. The checklist evaluates access control, rate limiting, and secure coding patterns to prevent vulnerabilities before deployment.

Does this security review cover both frontend and backend layers for sensitive data handling?▼

Yes, this security review covers both frontend and backend layers for sensitive data handling. It provides practical guidance for implementing security controls across user input, API design, and third-party integrations.

Why do I need a security checklist for reviewing access control and rate limiting in my code?▼

You need a security checklist for reviewing access control and rate limiting to systematically identify risks early in development. It ensures comprehensive coverage of authorization, secure coding patterns, and data handling before deployment.