Stats
Actions
Tags
From oplane
Analyze the current project for security threats and generate a threat model with implementation assessments
How this skill is triggered — by the user, by Claude, or both
Slash command
/oplane:analyzeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Perform a security threat model analysis on this codebase.
Perform a security threat model analysis on this codebase.
$ARGUMENTS
IMPORTANT: You MUST complete ALL steps below. Creating the threat model (step 4) is only the midpoint — you MUST also get implementation advice, assess every requirement against the actual code, and call update_implementation_state for each one. Do NOT stop after new_threatmodel returns.
Verify Oplane MCP tools are available (MANDATORY) — Call my_recent_threatmodels to verify the Oplane MCP connection is working. If this call fails or the tools are not available, STOP IMMEDIATELY. Do not proceed with any analysis. Report the error and tell the user to check the Oplane MCP server status: in Claude Code run /mcp, in Cursor open Settings > MCP. Never perform analysis without working Oplane tools — local-only results cannot be persisted and are not acceptable. If the call succeeds, also check for your existing threat models to avoid duplicates.
Explore the project — Understand what the application does, its tech stack, architecture, and security-critical components. Read the README, configuration files, route definitions, and key source files.
Identify scopes — Find threat modeling scopes:
Create threat models — Call new_threatmodel for each scope with a descriptive title and detailed change_description covering data flows, external services, and what could go wrong.
Assess every requirement — For each generated requirement:
a. Call request_implementation_advice in batches of 3–5 IDs (not all at once — large batches exceed output limits)
b. Search the codebase to verify implementation
c. Call update_implementation_state with your assessment and explanation
Adjust severity — If any requirement's severity doesn't match the actual risk context, use update_requirement_severity with a motivation note.
Summarize — Report the number of threat models, total requirements, implementation state breakdown, and key findings.
npx claudepluginhub oplane/oplane-plugin --plugin oplaneGenerates repo-specific threat models enumerating trust boundaries, assets, attacker capabilities, abuse paths, mitigations in Markdown. For explicit AppSec threat modeling requests.
Produces threat models for codebases or systems: identifies crown jewels assets, maps attack surface entry points and trust boundaries, ranks threats, suggests mitigations and accepted risks.