security
/security
This skill should be used when reviewing code for security vulnerabilities, performing security audits, or when the user asks about "security review", "vulnerability", "XSS", "CSRF", "injection", "race conditions", "OAuth security", "OIDC pitfalls", "timing attacks", or "access control". Provides a comprehensive vulnerability taxonomy and review methodology.
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
This skill should be used when reviewing code for security vulnerabilities, performing security audits, or when the user asks about "security review", "vulnerability", "XSS", "CSRF", "injection", "race conditions", "OAuth security", "OIDC pitfalls", "timing attacks", or "access control". Provides a comprehensive vulnerability taxonomy and review methodology.
Triggers from the description
Original author description
This skill should be used when reviewing code for security vulnerabilities, performing security audits, or when the user asks about "security review", "vulnerability", "XSS", "CSRF", "injection", "race conditions", "OAuth security", "OIDC pitfalls", "timing attacks", or "access control". Provides a comprehensive vulnerability taxonomy and review methodology.
How it works
- Common Vulnerability Classes
- Domain-Specific Concerns
- Review Methodology
- Severity Classification
SKILL.md preview
--- name: security description: This skill should be used when reviewing code for security vulnerabilities, performing security audits, or when the user asks about "security review", "vulnerability", "XSS", "CSRF", "injection", "race conditions", "OAuth security", "OIDC pitfalls", "timing attacks", or "access control". Provides a comprehensive vulnerability taxonomy and review methodology. version: 0.1.0 --- # Security Review Guide Comprehensive vulnerability taxonomy and review methodology for code security reviews. Project-specific security policies (CLAUDE.md, security docs) always take priority over this guidance. ## Common Vulnerability Classes ### Injection - **SQL injection**: Unsanitized user input in queries; use parameterized queries or ORM query builders - **Command injection**: User input passed to shell commands; avoid shell execution or use strict allowlists - **LDAP injection**: Unsanitized input in LDAP queries - **Header injection**: User input in HTTP headers enabling response splitting ### Cross-Site Scripting (XSS) - **Reflected**: User input echoed in responses without encoding - **Stored**: Persistent user input rendered without encoding - **DOM-based**: Client-side JavaScript manipulating DOM with unsanitized data ### Cross-Site Request Forgery (CSRF) - Missing or weak CSRF token validation - Token not bound to user session - GET requests performing state changes ### Authentication Flaws - Weak credential handling or storage - Insecure session management - Missing authentication checks on protected endpoints ### Authorization Flaws - Broken access control, privilege escalation - Insecure Direct Object References (IDOR) - Missing tenant isolation in multi-tenant systems ### Cryptographic Issues - Weak algorithms (MD5, SHA1 for security purposes) - Improper key management or hardcoded secrets - Insufficient entropy in token/nonce generation ### Information Disclosure - Sensitive data in logs, error messages, or API responses - Stack traces or debug info exposed in production - Credentials or tokens in URLs ### Insecure Deserialization - Unsafe parsing of untrusted data formats - Object instantiation from user-controlled input ## Domain-Specific Concerns ### Race Conditions - **TOCTOU bugs**: Time-of-check-to-time-of-use allowing business logic violations (double-spending, duplicate issuance) - **Concurrent access**: Missing locking or optimistic concurrency control on shared resources ### OAuth 2.0 Pitfalls - Token leakage via referrer headers or logs - Insufficient scope validation - Redirect URI manipulation (open redirect, partial matching) - Authorization code replay - PKCE bypass or missing PKCE enforcement - Refresh token rotation issues ### OpenID Connect Pitfalls - ID token validation gaps (signature, expiry, issuer, audience) - Nonce misuse or missing nonce validation - `at_hash` / `c_hash` verification omitted - Issuer confusion in multi-provider setups ### Session Security - Session fixation or hijacking - Insufficient expiration (idle and absolute timeouts) - Cookie attribute misconfiguration (missing Secure, HttpOnly, SameSite) ### Timing Attacks - Non-constant-time comparisons on secrets, tokens, or hashes — all secret comparisons (passwords, tokens, HMAC digests, API keys) must use constant-time operations (e.g., `ActiveSupport::SecurityUtils.secure_compare`, `hmac.compare_digest`, `crypto.timingSafeEqual`) - Observable timing differences in authentication flows (e.g., different response times for valid vs invalid usernames) - Database lookups that short-circuit on missing records before performing credential verification ## Review Methodology 1. **Read the actual code** — do not rely on summaries or assumptions; open and read every file under review and follow references to understand the full call chain 2. **Analyze each change** against the vulnerability classes above 3. **Check surrounding code** — vulnerabilities often arise from interactions between new and existing code 4. **Verify both presence and absence** — confirm mitigations exist where needed, and note areas reviewed that appeared secure ## Severity Classification - **Critical**: Remotely exploitable, no authentication required, leads to full system compromise or mass data breach - **High**: Exploitable with low complexity, leads to significant data exposure or privilege escalation - **Medium**: Requires specific conditions to exploit, limited blast radius - **Low**: Minor issue, difficult to exploit, minimal impact - **Informational**: Best practice deviation, defense-in-depth recommendation
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · sorah/config | 90 | MIT |
| flavien-ia/hypervibe-craft | 100 | Apache-2.0 |
| boshu2/agentops | 100 | Apache-2.0 |
| iamalisson/landspec | 100 | MIT |
| asckye/tia_portal_openness_mcp | 100 | MIT |
| Esposter/Esposter | 100 | Apache-2.0 |
| event4u-app/agent-config | 100 | MIT |
| motormetrics/motormetrics | 100 | MIT |
| motormetrics/motormetrics | 100 | MIT |
Database snapshot: 13.11.2026 · package version 07185abeb1fb (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100performing-security-code-review
This skill provides automated assistance for security agent tasks Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin. it analyzes code for potential vulnerabilities like sql injection, xss, authentication flaws, and… - 90security-audit
Use when reviewing code security, auditing dependencies for CVEs, checking configuration or secret security, assessing authentication and authorization patterns, identifying OWASP vulnerabilities (injection, XSS, CSRF), or addressing security concerns about implementations. - 100code-review-security
Security-focused code review checklist and automated scanning patterns. Use when reviewing pull requests for security issues, auditing authentication/authorization code, checking for OWASP Top 10 vulnerabilities, or validating input sanitization. Covers SQL injection prevention,… - 95vibe-security
Comprehensive secure coding guide covering OWASP web vulnerabilities with prevention patterns and checklists. Use when writing or reviewing web application code to prevent XSS, CSRF, SSRF, SQL injection, access control flaws, and other common security vulnerabilities. - 100security-expert
Expert defensive application security and secure code review (OWASP Top 10). Trigger keywords: security, vulnerability, OWASP, injection, SQL injection, XSS, CSRF, SSRF, authentication, authorization, access control, secrets, JWT, session, dependency, secure coding,… - 95aif-security-checklist
Security audit checklist based on OWASP Top 10 and best practices. Covers authentication, injection, XSS, CSRF, secrets management, and more. Use when reviewing security, before deploy, asking "is this secure", "security check", "vulnerability".