security-threat-model

Generate repo-grounded threat models enumerating assets, trust boundaries, entry points, and abuse paths.

1|1|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/RamonsDka/the-architect-overlay --skill security-threat-model-ramonsdka
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-threat-model
Source: https://github.com/RamonsDka/the-architect-overlay/tree/main/skills/security-threat-model
Command: npx skills add https://github.com/RamonsDka/the-architect-overlay --skill security-threat-model-ramonsdka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates repo-grounded threat models tailored to a codebase or project path, anchored to concrete evidence in the repository.

Core Features & Use Cases

  • Anchors architectural claims to repository evidence (files, paths, prompts) to produce actionable threat models.
  • Enumerates assets, trust boundaries, entry points, attacker capabilities, abuse paths, and mitigations.
  • Produces structured threat models that AppSec teams can use for risk assessment and remediation planning.

Quick Start

Provide a repo-scoped threat model for a target codebase using the guided workflow described in the SKILL.md.

Frequently Asked Questions about security-threat-model

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

FAQPage Schema
What is repo-grounded threat modeling for application security?▼

Repo-grounded threat modeling anchors architectural claims to concrete repository evidence, producing structured threat models that enumerate assets, trust boundaries, entry points, and abuse paths for AppSec review.

How do I generate an AppSec threat model from a codebase?▼

Apply the threat modeling Skill to a project path to analyze repository files and paths, producing a concise report enumerating assets, attacker capabilities, abuse paths, and mitigations suitable for risk assessment.

Can I use this threat model for an existing project path instead of a cloned repo?▼

Yes, you can apply the threat modeling workflow to any codebase or project path to extract repository evidence and generate a structured security analysis tailored to that specific project.

What's the best way to map trust boundaries and entry points during security analysis?▼

The best way is to anchor your security analysis to repository evidence, using the prompt templates to systematically enumerate trust boundaries, entry points, and attacker capabilities into a structured threat model.

Why does my threat model lack concrete evidence for architectural claims?▼

Threat models often lack concrete evidence when architectural claims are not properly referenced to repository files, paths, and prompt templates, which this Skill enforces to ensure actionable AppSec review.