security▌

Systematic security code review identifying high-confidence vulnerabilities with data-flow verification. \n \n Focuses exclusively on HIGH CONFIDENCE findings: vulnerable patterns with confirmed attacker-controlled input, skipping theoretical issues and framework-mitigated code \n Requires codebase research before reporting: traces data flow, checks for validation/sanitization, and verifies exploitability rather than pattern-matching alone \n Covers 14 vulnerability categories (injection, XSS, a

Use for reverse engineering stripped Go and Rust binaries including runtime recognition, pclntab/moduel data recovery, panic strings, and idiomatic decompilation recovery.

JWT authentication and authorization for Spring Boot 3.5.x with token generation, refresh strategies, and role/permission-based access control. \n \n Covers token generation with JJWT, Bearer/cookie authentication, and stateless session management using Spring Security 6.x \n Supports database-backed and OAuth2 provider integration (Google, GitHub) with modern SecurityFilterChain configuration \n Includes refresh token rotation, token blacklisting, and key rotation strategies for production secu

Provides reverse engineering techniques. Use when the main job is to understand how a compiled, obfuscated, packed, or virtualized target works before exploiting or solving it, including binaries, APKs, WASM, firmware, custom VMs, bytecode, malware-like loaders, and anti-debug or anti-analysis logic. Do not use it when the vulnerability is already understood and the remaining task is exploitation; use pwn instead. Do not use it for pure web workflows, log or disk forensics, or standalone crypto problems unless reversing the implementation is the real blocker.

Implement comprehensive security hardening with defense-in-depth strategy through coordinated multi-agent orchestration:

Comprehensive security rules for writing secure code across 15+ languages. Covers OWASP Top 10, infrastructure security, and coding best practices with 28 rule categories.

Generate ECS-compliant security events, multi-step attack scenarios, and synthetic alert documents that populate Elastic Security dashboards, the Alerts tab, and Attack Discovery.

Security Requirement Extraction \n Transform threat analysis into actionable security requirements. \n Use this skill when \n \n Converting threat models to requirements \n Writing security user stories \n Creating security test cases \n Building security acceptance criteria \n Compliance requirement mapping \n Security architecture documentation \n \n Do not use this skill when \n \n The task is unrelated to security requirement extraction \n You need a different domain or tool outside this sco

Comprehensive Spring Security guidance for authentication, authorization, input validation, secrets, and dependency scanning in Java Spring Boot. \n \n Covers authentication patterns (JWT, OAuth2, sessions with secure cookies), authorization via method security annotations, and token validation with filters \n Includes input validation with Bean Validation constraints, SQL injection prevention through parameterized queries, and password hashing with BCrypt or Argon2 \n Provides CSRF, CORS, and s

Philosophy: Non-opinionated, correctness-focused. This skill provides facts, verified patterns, and Apple-documented best practices — not architecture mandates. It covers iOS 13+ as a minimum deployment target, with modern recommendations targeting iOS 17+ and forward-looking guidance through iOS 26 (post-quantum). Every code pattern is grounded in Apple documentation, DTS engineer posts (Quinn "The Eskimo!"), WWDC sessions, and OWASP MASTG — never from memory alone.