0day-scannerLLM-powered zero-day vulnerability analysis of code changes — a commit, a pull request, a file or a branch — in light, standard or deep mode, with cost budgeting and knowledge-graph linking. Use whenever someone asks to scan for vulnerabilities, check for security issues, mentions 0-day or zero-day,
security-assessmentComprehensive OWASP Top 10 2025 and ASVS Level 1 security assessment across a whole codebase, with cost budgeting, knowledge-graph linking and automated test generation. Use whenever someone asks to run a security assessment, a security audit, a security check or a vulnerability assessment; mentions
security-reviewerMulti-language security review for web apps, APIs, and CLIs. Use whenever code is added or modified — new endpoints, auth/RBAC changes, template or DOM rendering, outbound HTTP, dependency updates, IaC/config changes, or end-of-feature reviews. Covers Python, JavaScript, TypeScript, Go, Rust, Java/K
threat-modelingAutomated STRIDE and DREAD threat modelling from code analysis. Extracts architecture, data flows, entry points and trust boundaries, then produces ranked threats, attack scenarios, mitigations and compliance-ready documentation. Use for security assessment, architecture review, compliance documenta
tm-quick-security-assessmentThe QUICK tier. Scope to a git worktree/branch and assess only what changed against a base — a fast, threat-model-aware pre-merge security pass (attack-surface delta + OWASP Top 10 on changed files) with the trust-direction gate applied. Composes the security-assessment + 0day-scanner (light) skills
tm-security-reviewThe COMPREHENSIVE tier. Build (or ingest) a full STRIDE threat model as input, then run a sophisticated whole-repo adversarial zeroday exploit review (triple-pass HUNT -> JUDGE -> VERIFY) that validates the model against the code and proves a runnable PoC per confirmed finding. Composes the threat-m