Install any skill in seconds. Free to start, no credit card required.
Get Started Free →codexstar69/threat-model-generation
Generate or refresh a STRIDE-based threat model for the current repository using Bug Hunter-native artifacts.
Passed 10 of 19 test cases with the skill, and 10 of 19 without it.
and 5 more in the full report
6 fixed11 passed either way2 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our CI script attempts to write security artifacts to `~/.config/bug-hunter/` or `.factory/`. Where should threat model artifacts strictly reside relative to the project root?
| Checked | Without skill | With skill |
|---|---|---|
| Restricts all generated security context artifacts strictly to the `.bug-hunter/` project subdirectory. | Missed | Passed |
The instructions your model reads when the skill loads.
This is a bundled local Bug Hunter companion skill. It generates portable threat-model artifacts under .bug-hunter/.
Create the security context that the other security skills depend on:
Write:
.bug-hunter/threat-model.md.bug-hunter/security-config.json.bug-hunter/triage.json if available for file structure and domain hints.prompts/threat-model.md is generated from this skill for older clients. This
skill is the canonical source and must be edited instead of the generated
compatibility prompt.
test cases passed, vs 10 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.