skills.rest
vigolium
vigoliumOFFICIAL
Explore all skills by this author →
Website𝕏@VigoliumGitHub

security-threat-model

Generate repository-grounded AppSec threat models with trust boundaries and mitigations.

965|142|Updated Mar 8, 2026
Search Tags:#threat modeling#appsec#mitigations#risk prioritization#abuse paths#repo grounding#attack surfaces
One-click install
npx skills add https://github.com/vigolium/vigolium --skill security-threat-model-vigolium
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-threat-model
Source: https://github.com/vigolium/vigolium/tree/main/platform/vigolium-audit/src/content/skills/security-threat-model
Command: npx skills add https://github.com/vigolium/vigolium --skill security-threat-model-vigolium

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of producing actionable, repository-specific threat models that go beyond generic checklists and instead map attacker goals to concrete trust boundaries and mitigations in your codebase.

Core Features & Use Cases

  • Repo-grounded abuse-path modeling: Enumerates trust boundaries, attacker capabilities, assets, and realistic abuse paths tied to evidence in the repository.
  • Prioritized risk calibration: Ranks threats using qualitative likelihood and impact reasoning tailored to the system context and any discovered controls.
  • Mitigation planning with evidence: Produces mitigation recommendations anchored to concrete components, boundaries, and entry points, and includes detection ideas.

Quick Start

Ask the AI to threat model this repository or a specific codebase path (for example: “Create a repository-grounded threat model for vigolium focusing on the CLI and scanning workflows under /src”).

Frequently Asked Questions about security-threat-model

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

FAQPage Schema
How do I generate a threat model for a specific codebase path?▼

Threat modeling analyzes a codebase to enumerate trust boundaries, assets, and realistic abuse paths. It maps attacker goals to concrete components and mitigations, moving beyond generic checklists to provide actionable, repository-specific security analysis.

Can I prioritize security risks based on my system's specific context?▼

Yes, risk prioritization ranks threats using qualitative likelihood and impact reasoning tailored to your system's context. It calibrates threat severity based on discovered controls and specific attacker capabilities mapped during the repository analysis.

Does threat modeling work for analyzing specific components like a CLI scanning workflow?▼

Yes, you can target threat modeling at specific components like a CLI and its scanning workflows by providing the explicit repository path. The analysis grounds abuse path discovery and mitigation planning in evidence found within that targeted code scope.

What is the best way to map mitigations to attack surfaces in a repository?▼

The best way to map mitigations to attack surfaces is through evidence-based discovery that anchors recommendations to concrete components, trust boundaries, and entry points. This approach ensures mitigation planning includes specific detection ideas tied to your codebase.

Related Skills

Explore More Software Engineering Skills→
jaypatrickjaypatrick

security-threat-model

Identify components, data stores, entry points, and trust boundaries from repository evidence.

Community
Advanced
shirulotshirulot

security-threat-model

Generate repository-grounded threat models from trust boundaries, assets, and entry points.

Community
Advanced
langbyyilangbyyi
96

graphql-and-hidden-parameters

Identify GraphQL API vulnerabilities including hidden parameters and authorization gaps.

Community
Advanced
YairamaYairama

security-threat-model

Generate repository-grounded threat models identifying trust boundaries, assets, attack paths, and risks.

Community
Advanced