security

Name: security
Availability: InStock
Author: SleepyDreamsDev

Identify and remediate security risks in Git diffs with OWASP Top 10 checks.

Updated Aug 23, 2026

Search Tags:#authorization #security #authentication #vulnerability #owasp #threat-modeling #code-review

Ready to run

npx skills add https://github.com/SleepyDreamsDev/claude-tdd-starter --skill security-sleepydreamsdev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security
Source: https://github.com/SleepyDreamsDev/claude-tdd-starter/tree/main/core/.claude/skills/security
Command: npx skills add https://github.com/SleepyDreamsDev/claude-tdd-starter --skill security-sleepydreamsdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep security reviews of recent code changes, performing threat modeling, OWASP Top 10 checks, auth/authz validation, input sanitization review, and actionable fix suggestions. Use before PRs, after implementing features, or when the user asks for security checks.

Core Features & Use Cases

Threat modeling and risk assessment across changes.
OWASP Top 10 checks, authentication/authorization validation, and input sanitization reviews.
Actionable fixes and security reporting to strengthen PR hygiene and post-merge quality.
Use case: when preparing a PR, run a security review to surface vulnerabilities and recommended mitigations.

Quick Start

Launch a security review on your current changes by invoking the /security command.

Frequently Asked Questions about security

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

FAQPage Schema

How do I run a security review on my code changes before a pull request?▼

Run a security review by invoking the /security command on your current Git diffs or specific file sets. It performs threat modeling, OWASP Top 10 checks, and authentication validation, then outputs a structured Security Review Report with actionable fixes.

What does threat modeling for code changes involve?▼

Threat modeling for code changes involves a phased workflow: scoping the changes, building a threat model, reviewing the code, and generating a report. This process surfaces threats across API, authentication, data handling, and configuration areas.

Can I check my unstaged Git changes for OWASP Top 10 vulnerabilities?▼

Yes, you can scan unstaged Git changes or the previous commit for OWASP Top 10 vulnerabilities. The security review identifies risks like input sanitization flaws and authorization issues, providing recommended mitigations.

Does this security review validate both authentication and authorization logic?▼

Yes, the security review validates both authentication and authorization logic within your code changes. It checks for proper auth and authz implementation alongside input sanitization reviews to ensure comprehensive API and data handling protection.

When should I perform a code security review on my feature implementation?▼

Perform a code security review after implementing features or before submitting a PR. Running the review at these stages surfaces vulnerabilities and provides actionable fixes to strengthen PR hygiene and post-merge quality.

What is the best way to find configuration and data handling risks in a recent commit?▼

The best way to find configuration and data handling risks is running a security review on the previous commit. The review applies threat modeling and OWASP checks to your diffs, generating a structured report with identified threats and remediation suggestions.