Skip to content
Get packs

Threat Modeling Your Estate

Maps sensitive data, trust boundaries and compromise scenarios, and keeps a scored risk register.

Source Download skill
Repository
danielmiessler/LifeOS
Stars
19,682
Licence
MIT
Files
9 files

What it does

Once installed, the agent can help you think like a defender about your own systems. It finds where sensitive data lives, imagines what happens if a given asset were compromised, maps where untrusted text could sneak into the agent, and records scored risks in a register that gets reviewed over time. It is designed to model your setup, not to attack it, and it keeps secret values out of its output.

Great for

  • Developers or operators who run their own servers, services and AI agent setups and want a structured security review
  • Small teams who need a written risk register with owners and review dates
  • Anyone asking 'how exposed am I' or 'what if this got hacked' about their own estate

Skip it if

  • Active penetration testing or scanning of systems: the skill explicitly excludes exploitation and scanning, and the description points to a separate offensive skill for that
  • Live incident response: the skill excludes running IR, so it is not a substitute for responders during an active breach
  • Assessing systems you do not own or have no inventory of, since without an asset list the output rests on guesses

Try asking

  • “Run a full security audit of my estate and tell me where the biggest risks are”
  • “What if my deploy token got hacked? Show the blast radius.”
  • “Map where our sensitive customer data is stored and flag assets that are unclassified”
  • “Add a risk to the register: the staging server has public SSH, and review its score”
Step-by-step guide: how to use Threat Modeling Your EstateInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 9 original files, the MIT licence and an attribution note.

    ThreatModel.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip ThreatModel.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip ThreatModel.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Give the skill a hand-written list of your assets and data types, since without Atlas it can only work from what you tell it and the repo or config files it inspects.
  • Review the generated register regularly; the skill is built to surface risks for periodic review rather than one-off reports.
  • Keep credentials out of prompts: the register stores only environment variable names, so do the same when describing your setup.

What's inside

  • Intents/CompromiseScenario.md
  • Intents/InjectionSurfaceMap.md
  • Intents/RiskRegister.md
  • Intents/SecurityAudit.md
  • Intents/SensitiveDataMap.md
  • Intents/ThreatModelTarget.md
  • References/Continuous.md
  • SKILL.md
  • Tools/RiskRegister.ts

Redistributed unmodified from danielmiessler/LifeOS under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.