<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Threat-Modeling on Vibe Coding</title><link>https://vibecoding.rest/tags/threat-modeling/</link><description>Recent content in Threat-Modeling on Vibe Coding</description><generator>Hugo</generator><language>en</language><atom:link href="https://vibecoding.rest/tags/threat-modeling/index.xml" rel="self" type="application/rss+xml"/><item><title>Security Threat Model Skill</title><link>https://vibecoding.rest/skills/security-threat-model-skill/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/security-threat-model-skill/</guid><description>&lt;p&gt;This curated Codex skill walks through producing a structured threat model for a system — assets, trust boundaries, and attack surfaces — rather than an ad hoc security discussion.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Threat modeling is only useful if it&amp;rsquo;s structured and complete; an unstructured conversation tends to miss entire categories of risk. A skill that enforces the methodology produces a threat model that&amp;rsquo;s actually useful to a security reviewer.&lt;/p&gt;</description></item></channel></rss>