security

Identify and mitigate security risks in features handling user data and authentication.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/saranskumar/anti-slop --skill security-saranskumar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security
Source: https://github.com/saranskumar/anti-slop/tree/main/archive/skills-legacy/security
Command: npx skills add https://github.com/saranskumar/anti-slop --skill security-saranskumar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use this skill ensures security considerations are embedded when building features that touch user data, authentication, APIs, file uploads, permissions, or external integrations, and it can serve as a review pass before marking any feature as done.

Core Features & Use Cases

  • Map the attack surface: identify inputs, data flows, access controls, and potential misuses.
  • Input security: enforce validation, type-safety, and safe handling of user-provided data.
  • Auth & Authorization: ensure authentication requirements and proper permission checks; enforce ownership and server-side checks for admin routes.
  • Data exposure: limit responses to authorized data and avoid leaking secrets.
  • Transport & Environment: enforce HTTPS, secrets in env vars, and correct CORS.
  • Dependency & Audit checks: verify libraries do not have critical CVEs and run audits before release.
  • Review-as-you-build: security considerations should be integrated throughout the development process.

Quick Start

Initiate a security review for any feature touching user data, authentication, APIs, file uploads, or external integrations before development proceeds.

Frequently Asked Questions about security

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

FAQPage Schema
How do I conduct a security review for features handling user data and APIs?

A security review maps the attack surface of features handling user data and APIs by identifying inputs, data flows, and access controls. It enforces input validation, proper authentication checks, and data minimization before release.

What is threat modeling and how does it apply to secure development?

Threat modeling in secure development identifies potential misuses across inputs, data flows, and access controls. It documents security findings and applies fixes throughout the feature lifecycle to mitigate risks before deployment.

How do I enforce authorization and access controls for admin routes?

Enforcing authorization for admin routes requires implementing server-side permission checks and ownership validation. A security review verifies that authentication requirements are met and responses limit data exposure to authorized users only.

When do I need a dependency audit before releasing a feature?

A dependency audit is needed before releasing any feature with external integrations or libraries. The security review process verifies libraries do not have critical CVEs and runs audits to ensure secure transport and environment configuration.

Does this security review process work for file uploads and external integrations?

Yes, the security review process works for file uploads and external integrations by enforcing input validation, type-safety, and safe handling of user-provided data. It scopes design reviews, access controls, and data minimization across typical feature lifecycles.

What's the best way to prevent data exposure and secret leaks in API responses?

Preventing data exposure requires limiting API responses to authorized data and storing secrets in environment variables. A security review checks for correct CORS, HTTPS enforcement, and ensures sensitive data is not leaked in responses.