threat-modeling is agent-read markdown (skill) from miosa-osa/osa: Build a concrete cyber defense threat model from assets, data flows and trust boundaries, then map controls to attack simulations and verification. Use for threat modeling, architecture security, abuse cases or designing defenses before deployment..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Threat Modeling
## Workflow
1. Read the system architecture and identify assets, entry points, actors and trust boundaries. Record assumptions you cannot verify.
2. For each sensitive flow, construct a concrete misuse case with prerequisites, affected asset and observable failure.
3. Choose a control with an owner and verification method, not just a framework label.
4. Read the worked boundary example and map only supported behaviors to cyber_defense fixtures.
5. Test relevant implementation paths and benign behavior; prioritize residual risks with evidence.
6. Revisit the model when architecture or trust assumptions change. A successful generic lab does not validate the deployed application.
## Worked example and prerequisites
Read [references/workflow.md](references/workflow.md) before execution. Use only registered OSA tools named in the frontmatter; command examples run through `shell_execute`. Check `command -v` for each external executable on the actual target. Optional packages, external collectors and vendor accounts are not bundled or presumed installed.
## Evidence and completion
…
Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
GET https://markdownregistry.com/api/v1/artifacts/art_gburicaeouzbvnye
GET https://markdownregistry.com/api/v1/resolve?ref=miosa-osa/osa/threat-modeling
GET https://markdownregistry.com/api/v1/blob/dd84bcb8b894549f1c68c8e8efb475ea15a7c718611e8e70be20a36bd30ac850
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
miosa-osa/osa · examples/skills/meeting-prep/SKILL.md · Research attendees, prepare talking points, and summarize previous interactions before meetings
timwukp/agent-skills-best-practice · skills/skills/threat-modeling/SKILL.md · Performs STRIDE threat modeling for features, APIs, and architecture changes, producing a threat model document with…
cristhianzl/claude-skills-czl · configs/langflow/skills/threat-modeling/SKILL.md · Structured security design analysis — find what can go wrong before an attacker does. Build a Data Flow Diagram with…
cristhianzl/claude-skills-czl · configs/agnostic/skills/threat-modeling/SKILL.md · Structured security design analysis — find what can go wrong before an attacker does. Build a Data Flow Diagram with…
okhp3/skillz · community/threat-modeling/SKILL.md · Works out what could go wrong in a system's design before it is built — who would attack it, how, and which defences…
aniruddhadas1/oniroute_swarmagents · skills/official/security/threat-modeling/SKILL.md · Identify assets, trust boundaries, threats, and mitigations before risks become incidents. Use for planning…
