Individual skill
omh-application-threat-model
[omh] Attack paths into an operated system: turn a system's components and data flows into assets, trust boundaries, attack scenarios, controls, and the security test that proves each control holds. Use when the user says: application-threat-model, application threat model, threat model, threat modeling, threat modelling, threat modeling session, threat modeling workshop, security threat model.
skills/omh-application-threat-model/SKILL.md
Source commit 98284f305f6a9dce6e36a1580c9f333105f1a950
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 5,442
- Repository last updated
- Nov 11, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent Repository topic
- ai Repository topic
- ai-agent Repository topic
- ai-tools Repository topic
- claude-code Repository topic
- codex Repository topic
- hermes-agent Repository topic
- hermes-skill Repository topic
- skills Repository topic
- security Derived category
- data Derived category
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 10,830 bytesreferences/threat-model-method.mddoc · 5,328 bytes
Read excerpt
# Application Threat Model
This is a Hermes-native `application-threat-model` workflow skill.
## Why This Exists
`application-threat-model` exists because the nearest neighbour does not merely miss this request. `security-safety-review` maps the agent's own prompt, tool, credential, and dependency surface, so an application threat-model request came back as an agent tool inventory under a near-identical name — a confident wrong artifact rather than a miss, in the one domain where that costs most.
## Do Not Use When
- The subject is the agent's own prompts, tools, files, credentials, dependencies, or destructive actions; use `omh-security-safety-review`, which maps that runtime surface.
- The user wants defects found in a diff or a file; use `omh-code-review`.
- The user asks whether a release is ready across rollout, rollback, and observability; use `omh-production-audit`.
- The user asks which commands prove a merge is safe; use `omh-verification-gate`.