--- title: "Threat Modeling Expert: review, role & definition · Undominated.ai" canonical: https://undominated.ai/agents/wshobson-threat-modeling-expert/ description: "Structures a security design review around trust boundaries, data flows, attack paths, mitigations and residual risks." --- # Threat Modeling Expert: review, role & definition · Undominated.ai > Structures a security design review around trust boundaries, data flows, attack paths, mitigations and residual risks. [← Explore all agents](/agents/) SECURITY AND GOVERNANCE / wshobson # Threat Modeling Expert Structures a security design review around trust boundaries, data flows, attack paths, mitigations and residual risks. Use this definition ↓Original source ↗ SOURCE REVIEW Reviewed 2026-09-21 Evidence 4 linked sources Publisher wshobson Licence MIT ↗ Revision 4236bb91f839 Read what was—and wasn’t—checked ↓ “Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use PROACTIVELY for security architecture” wshobson · upstream description ↗ Our analysis follows below. 01 / THE REASONING ## Why this made the selection. - Provides a concrete sequence from scope and assets through STRIDE and attack trees to documented residual risk. - Connects threats to security requirements and asks for mitigation tracking as the architecture changes. ### A good fit for - Preparing a threat-model workshop for a new service or feature. - Reviewing an architecture's trust boundaries before implementation. ### Weigh up before choosing - This is a design-review role, not a scanner, penetration test or compliance certificate. - The prompt does not define a specific report schema or risk-scoring method; agree those with the team. - The opus alias and inherited tool permissions depend on the host configuration. 02 / THE REVIEW RECORD ## What we actually inspected. Source review has boundaries. A clear record is more useful than a “safe” badge. ### Material inspected - plugins/security-scanning/agents/threat-modeling-expert.md (complete frontmatter and body) - LICENSE (applicable redistribution terms) - README.md (host and installation guidance) - Host configuration documentation; immutable source and licence hashes ### Our findings - The workflow starts with scope and data flows before assessing components. - It names insider threats and residual risk, rather than implying that proposed mitigations remove every risk. - No explicit tool allowlist or external security service is bundled. ### Not established by this review - The agent has not been executed or benchmarked. - Tool availability, host/model compatibility and task outcomes were not runtime-tested. The review applies to the material and revision named here. A newer upstream release can change its behavior. 03 / PUT IT TO WORK ## Use the role in your project. Upstream setup instructions ↗ - Download the original threat-modeling-expert.md together with its LICENSE and attribution; inspect its instructions, model choice and tools. - For project use, place the definition in .claude/agents/threat-modeling-expert.md; the documented personal scope is ~/.claude/agents/. - Ask Claude Code to delegate a bounded task to the agent by its frontmatter name. Existing agent directories are watched; restart if you created a new agents directory after the session began. - Configure any referenced tools, sibling files or plugin dependencies separately. A standalone definition does not install its complete upstream plugin. ### Before you start - Claude Code with architecture diagrams, data flows, assets and trust-boundary context. - A scoped threat-model objective and developers able to validate system assumptions. ### Compatibility Claude Code subagents ### Host-mediated repository and tool access - No tools are restricted in frontmatter; Claude Code's available tools and permissions apply. - The role describes design analysis, not an authorization to probe or alter live systems. ### Cost model Definition can be reused under its stated licence. Host subscriptions, model usage or connected services may incur charges. THE COMPLETE REVIEWED DEFINITION ## Read it before you reuse it. Original source bytes, with attribution. Review the host-specific setup notes above. Copy definition ↗ [Download definition + licence ↗](/resources/agents/wshobson-threat-modeling-expert/bundle.zip)[Raw Markdown ↗](/resources/agents/wshobson-threat-modeling-expert/definition.md) --- name: threat-modeling-expert description: Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use PROACTIVELY for security architecture reviews, threat identification, or building secure-by-design systems. model: opus --- # Threat Modeling Expert Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use PROACTIVELY for security architecture reviews, threat identification, or building secure-by-design systems. ## Capabilities - STRIDE threat analysis - Attack tree construction - Data flow diagram analysis - Security requirement extraction - Risk prioritization and scoring - Mitigation strategy design - Security control mapping ## When to Use - Designing new systems or features - Reviewing architecture for security gaps - Preparing for security audits - Identifying attack vectors - Prioritizing security investments - Creating security documentation - Training teams on security thinking ## Workflow 1. Define system scope and trust boundaries 2. Create data flow diagrams 3. Identify assets and entry points 4. Apply STRIDE to each component 5. Build attack trees for critical paths 6. Score and prioritize threats 7. Design mitigations 8. Document residual risks ## Best Practices - Involve developers in threat modeling sessions - Focus on data flows, not just components - Consider insider threats - Update threat models with architecture changes - Link threats to security requirements - Track mitigations to implementation - Review regularly, not just at design time The download contains threat-modeling-expert.md . Keep its filename when placing it in the agent directory described above. By **wshobson**. Exact upstream source ↗ · [Licence](/resources/agents/wshobson-threat-modeling-expert/LICENSE.txt) · [Attribution](/resources/agents/wshobson-threat-modeling-expert/ATTRIBUTION.txt) SHA-256 43996cc279e63aeae24a036f8670d7d7c589d80176ee133adc9dc5d9a8561386 Read the applicable licence MIT License Copyright (c) 2024 Seth Hobson Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. 04 / FOLLOW THE EVIDENCE ## The source trail. Our notes are separate from the original resource. Check upstream before adopting a new version. - Threat Modeling Expert — complete upstream definition ↗ Checked 2026-09-21 https://github.com/wshobson/agents/blob/4236bb91f8395b0435f1d8b8baf9e8e4c69a8620/plugins/security-scanning/agents/threat-modeling-expert.md Supports: summary, upstreamDescription, whySelected, bestFor, limitations, review, access - Applicable upstream licence ↗ Checked 2026-09-21 https://github.com/wshobson/agents/blob/4236bb91f8395b0435f1d8b8baf9e8e4c69a8620/LICENSE Supports: license, artifact - Repository installation and scope guidance ↗ Checked 2026-09-21 https://github.com/wshobson/agents/blob/4236bb91f8395b0435f1d8b8baf9e8e4c69a8620/README.md Supports: compatibility, install - Host custom-agent configuration documentation ↗ Checked 2026-09-21 https://code.claude.com/docs/en/sub-agents.md Supports: compatibility, install, access, review, limitations KEEP COMPARING ## Other approaches to consider. Related by category or shared topics. These are alternatives to inspect, not a measured quality order. [### AI-DLC Compliance Agent ↗ Organizes data classification, requirement-to-control mapping and compliance evidence into an advisory role within an AI-DLC project.](/agents/awslabs-aidlc-compliance/)[### Se: Responsible Ai ↗ Screens user-facing changes for accessibility, privacy and exclusion concerns, then documents decisions and escalation needs in numbered responsible-AI records.](/agents/github-se-responsible-ai-code/)[### Security Auditor ↗ Reviews application code with a stack-specific security checklist, requiring source locations, exploit scenarios, concrete remediation and masked secrets in each finding.](/agents/anthropic-security-auditor/) [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)