Enforce database security for schema design, access control, encryption, and operational hardening. Use when building, reviewing, or auditing database schemas, connection handling, credential management, or database deployment configuration.
Apply defense-in-depth by layering multiple independent security controls. Use when reviewing system architecture, evaluating whether a single control is the only barrier, or assessing blast radius of a component compromise.
Creates devcontainers with language-specific tooling (Python/Node/Rust/Go) and persistent volumes. Use when adding devcontainer support to a project or setting up isolated development environments.
Enforce authorization server metadata discovery for MCP ecosystems. Use when configuring or reviewing authorization server endpoint publication and discovery metadata.
Enforce support for OAuth 2.0 and OIDC discovery mechanisms in MCP clients. Use when building, configuring, or reviewing MCP client authentication and authorization server discovery.
Support OAuth 2.0 Dynamic Client Registration in authorization servers. Use when building or reviewing authorization server client management for MCP ecosystems.
Enforce encrypted communication with external data sources. Use when designing, configuring, or reviewing network connections between AI systems and external databases, APIs, or data services.
Enforce MCP server integration with external centralized identity providers. Use when building, configuring, or reviewing MCP server authentication against external IdPs like Keycloak.
Protect LLM model files against unauthorized access and modification. Use when designing, deploying, or reviewing storage and access controls for AI model files and weights.
Enforce FIPS 140-2/140-3 compliance for RHEL, OpenShift, and Go workloads. Use when building, configuring, reviewing, or auditing systems that require FIPS-validated cryptographic modules, RHEL crypto-policy enforcement, FIPS-ready Go binaries, or FIPS-mode kernel and cluster configuration.
Core threat analysis engine. Takes a system context profile and applies one or more threat modeling frameworks (STRIDE, PASTA, LINDDUN, VAST, Attack Trees, OCTAVE) with automatic threat actor profiling.
Discovers system context for threat modeling through code analysis and/or user interview. Produces a structured system profile covering components, data flows, trust boundaries, assets, and entry points.
Reviews an existing THREATMODEL.md against the current codebase. Identifies stale threats, new attack surface, drift from assumptions, and unimplemented mitigations.
Main dispatcher for threat modeling. Routes to discover, analyze, and report sub-skills based on user intent. Supports multiple frameworks (STRIDE, PASTA, LINDDUN, VAST, Attack Trees, OCTAVE) and automatic threat actor profiling.