security-threat-review

Map attack surfaces and mitigation options for endpoints, authentication, and integrations.

Updated Aug 27, 2026

Search Tags:#security #authentication #risk-assessment #data-protection #threat-modeling #endpoints #integrations

Ready to run

npx skills add https://github.com/claushaas/claus-haas-ai-stuff --skill security-threat-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security-threat-review
Source: https://github.com/claushaas/claus-haas-ai-stuff/tree/main/skills/security-threat-review
Command: npx skills add https://github.com/claushaas/claus-haas-ai-stuff --skill security-threat-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Security review and pragmatic threat modeling for endpoints, authentication, sensitive data, and integrations in software projects.

Core Features & Use Cases

Pragmatic threat discovery: identify real-world threats based on repo context and system boundaries.
Attack surface mapping: enumerate endpoints, data flows, and external integrations.
Mitigation planning: provide multiple options with trade-offs and concrete next steps.
Governance-ready outputs: produce actionable recommendations suitable for development and security reviews.

Quick Start

Use this skill to perform a threat-modeling pass on the current repository focusing on user input, authentication, and data handling.

Frequently Asked Questions about security-threat-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I perform security threat modeling for API endpoints and authentication flows?▼

Security threat modeling for API endpoints and authentication flows is performed by analyzing repository context to enumerate attack surfaces, map data flows, and generate mitigation options with trade-offs. The process produces defensible, context-aware security decisions suitable for developer review.

What is pragmatic threat modeling for software codebases?▼

Pragmatic threat modeling for codebases is a security review approach that identifies real-world threats based on system boundaries and repository context. It maps attack surfaces across endpoints, sensitive data handling, and external integrations to produce actionable recommendations.

How do I identify attack surfaces for webhooks and external service integrations?▼

Attack surfaces for webhooks and external service integrations are identified by enumerating endpoints, data flows, and external dependencies within the repository context. This threat discovery process maps external service boundaries and generates mitigation options with concrete next steps.

Can I use this threat modeling approach for new user inputs and payment token flows?▼

Threat modeling for new user inputs and payment token flows is supported by analyzing sensitive data handling and API surfaces in the repository context. The approach generates assumptions, attack surfaces, and mitigation options specifically tailored to token flows and user input validation.

Does this security review method require external security tools or dependencies to run?▼

No external security tools or dependencies are required to perform this security review. The threat modeling operates directly on repository context to analyze endpoints, authentication mechanisms, and integrations, producing governance-ready outputs for development and security reviews.

What is the best way to generate governance-ready security recommendations for a repository?▼

Governance-ready security recommendations are generated by performing a threat-modeling pass on the repository focusing on user input, authentication, and data handling. This produces defensible, context-aware decisions with actionable recommendations and threat mappings suitable for security reviews.