Forge-Threat-Modelling

Identifies assets, trust boundaries, threats, and mitigations during system architecture design.

Updated Jul 18, 2026
One-click install
npx skills add https://github.com/Nealsch/ForgeOS --skill forge-threat-modelling-nealsch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Forge-Threat-Modelling
Source: https://github.com/Nealsch/ForgeOS/tree/main/Framework/05-Skills/02-Architecture/Forge-Threat-Modelling
Command: npx skills add https://github.com/Nealsch/ForgeOS --skill forge-threat-modelling-nealsch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security is often considered only after implementation, when fixing design flaws is expensive. This Skill embeds threat modelling into the architecture phase so teams can identify how systems may be misused, what assets need protection, and which controls should be designed in before any code is written. ## Core Features & Use Cases - Structured Threat Analysis: Follows a seven-step procedure covering system context, asset identification, trust boundaries, threat identification, risk assessment, mitigations, and documentation. - STRIDE-Based Threat Categories: Analyses spoofing, tampering, repudiation, information disclosure, denial of service, and elevation of privilege across attack surfaces and trust boundaries. - Template-Driven Outputs: Produces a documented Threat Model with asset inventory, trust boundary analysis, risk assessment, recommended mitigations, and residual risks using the Threat-Model template. - Use Case: When designing a new service that handles user credentials and integrates with third-party APIs, apply this Skill to map trust boundaries, identify likely attack paths, and recommend architectural controls before development starts. ## Quick Start Apply the Forge-Threat-Modelling skill to analyse the proposed system architecture and produce a threat model with identified assets, trust boundaries, risks, and recommended mitigations.

Frequently Asked Questions about Forge-Threat-Modelling

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

FAQPage Schema
How do I perform threat modelling during system design?▼

Follow a seven-step procedure: understand system context, identify assets, map trust boundaries, identify threats, assess risk by likelihood and impact, recommend mitigations, and document outcomes. Capture results in a Threat Model template for traceability.

What is STRIDE threat modelling and when should I use it?▼

STRIDE categorises threats into spoofing, tampering, repudiation, information disclosure, denial of service, and elevation of privilege. Use it when analysing attack surfaces and trust boundaries during architecture design to systematically uncover potential misuse.

When should threat modelling be applied in a project?▼

Apply it when designing a new system, introducing authentication or authorisation, handling sensitive data, adding external integrations, changing system boundaries, or reviewing significant architectural changes. It is not intended for routine code changes with no security impact.

Does threat modelling replace penetration testing or vulnerability scanning?▼

No. Threat modelling is a design-phase activity that identifies potential risks and recommends architectural controls. It does not perform penetration testing, vulnerability scanning, or implement security controls, and it does not guarantee system security.

What inputs are needed to start a threat model?▼

You need architecture context (system boundaries, components, data flows, integration points), data context (information assets, ownership, sensitivity, storage locations), and requirements (security expectations, compliance needs, user roles, business risks).