security-review

Review API endpoints, frontend code, and MCP server configurations for security vulnerabilities.

5|1|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/slashwhy/super-todo --skill security-review-slashwhy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-review
Source: https://github.com/slashwhy/super-todo/tree/main/.github/skills/security-review
Command: npx skills add https://github.com/slashwhy/super-todo --skill security-review-slashwhy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive checklist to identify and mitigate security vulnerabilities across your application's stack, from AI-generated code to infrastructure configurations.

Core Features & Use Cases

  • AI-Assisted Development Risks: Detects common pitfalls in AI-generated code like hallucinated packages and insecure defaults.
  • MCP Server Security: Audits configurations for hardcoded credentials, excessive permissions, and unvetted servers.
  • API & Frontend Security: Checks for common web vulnerabilities such as mass assignment, XSS, CSRF, and secrets exposure.
  • Use Case: Before merging a pull request that includes AI-generated code, use this Skill to perform a thorough security audit, ensuring no critical vulnerabilities are introduced.

Quick Start

Run a security review on the new API endpoint implementation.

Frequently Asked Questions about security-review

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

FAQPage Schema
How do I check AI-generated code for security vulnerabilities before merging?

To check AI-generated code for security vulnerabilities, run a security review targeting common AI pitfalls like hallucinated packages and insecure defaults. This process identifies risks such as hardcoded credentials and mass assignment before you merge the pull request.

What is the best way to audit MCP server configurations for security risks?

The best way to audit MCP server configurations is by running a targeted security review that checks for hardcoded credentials, excessive permissions, and unvetted servers. This audit utilizes a structured reporting format to calculate a specific risk score.

How do I identify API and frontend vulnerabilities like XSS and CSRF in my code?

To identify API and frontend vulnerabilities like XSS and CSRF, perform a comprehensive security review on your endpoints and data handling logic. This check detects mass assignment, SQL injection, and secrets exposure across your application stack.

Can I use this security review to check for hardcoded credentials and insecure defaults?

Yes, you can use this security review to check for hardcoded credentials and insecure defaults. It scans your application stack and infrastructure configurations to identify and mitigate these specific security risks.

Does this security review cover OWASP vulnerabilities in API endpoints and data handling?

Yes, this security review covers OWASP vulnerabilities in API endpoints and data handling. It identifies common web risks including SQL injection, cross-site scripting (XSS), cross-site request forgery (CSRF), and mass assignment.