Agent skill

Threat Model Generation

by codexstar69 in codexstar69/bug-hunter

Generate or refresh a STRIDE-based threat model for the current repository using Bug Hunter-native artifacts.

MITAuto-check passedSecurity

Install Threat Model Generation

skills CLI
$ npx skills add codexstar69/bug-hunter --skill threat-model-generation -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install codexstar69/bug-hunter threat-model-generation --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/codexstar69/bug-hunter.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/threat-model-generation .claude/skills/threat-model-generation && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
threat-model-generation
GitHub stars
519
Token cost
~408 tokens
SKILL.md length
154 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Generate or refresh a STRIDE-based threat model for the current repository using Bug Hunter-native artifacts.

  • Works in 4 steps: Read .bug-hunter/triage.json if… → Inspect the repository to identify → Generate a concise STRIDE threat model. → …
  • The repository has no threat model yet
  • SKILL.md covers Purpose, Required outputs, Workflow and Compatibility, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Threat Model Generation is an agent skill from codexstar69/bug-hunter. Generate or refresh a STRIDE-based threat model for the current repository using Bug Hunter-native artifacts. Use whenever the repository has no threat model yet, the architecture changed materially, a security review needs fresh trust-boundary context, or the user explicitly asks for a threat model.

Its SKILL.md is about 410 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Security, covering Threat modeling. The repository describes itself as: Adversarial AI bug hunter with auto-fix skill for Claude Code, Cursor, Codex CLI, GitHub Copilot CLI, Kiro CLI, Opencode, Pi Coding Agent, and more. Multi-agent pipeline finds… The licence is MIT.

When your agent uses it

  • The repository has no threat model yet
  • The architecture changed materially
  • A security review needs fresh trust-boundary context
  • The user explicitly asks for a threat model

Example prompts

  • “/threat-model-generation”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Read .bug-hunter/triage.json if available for file structure and domain hints.
  2. Inspect the repository to identify
  3. Generate a concise STRIDE threat model.
  4. Generate a matching security config with thresholds and tech-stack metadata.

What it can do on your machine

Read from SKILL.md and the folder at commit 3be6973. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Threat Model Generation loads about 408 tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 154 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~81
When it runs · the whole SKILL.md, loaded when a task matches
~408

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from codexstar69/bug-hunter at commit 3be6973, republished under its MIT licence (© codexstar69). 154 words, ~408 tokens.

Download SKILL.mdSave it as .claude/skills/threat-model-generation/SKILL.md (or your agent's skills folder).
name
threat-model-generation
description
Generate or refresh a STRIDE-based threat model for the current repository using Bug Hunter-native artifacts. Use whenever the repository has no threat model yet, the architecture changed materially, a security review needs fresh trust-boundary context, or the user explicitly asks for a threat model.

Threat Model Generation

This is a bundled local Bug Hunter companion skill. It generates portable threat-model artifacts under .bug-hunter/.

Purpose

Create the security context that the other security skills depend on:

  • trust boundaries
  • major components
  • STRIDE threats
  • vulnerability pattern library
  • severity/config defaults

Required outputs

Write:

  • .bug-hunter/threat-model.md
  • .bug-hunter/security-config.json

Workflow

  1. Read .bug-hunter/triage.json if available for file structure and domain hints.
  2. Inspect the repository to identify:
    • languages and frameworks
    • public/authenticated/internal entry points
    • data stores and external integrations
    • sensitive assets and trust boundaries
  3. Generate a concise STRIDE threat model.
  4. Generate a matching security config with thresholds and tech-stack metadata.

Compatibility

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.

Output rules

  • Keep the threat model short enough for downstream agents to consume.
  • Be specific about trust boundaries and vulnerable code patterns.
  • Keep all artifacts under .bug-hunter/, never .factory/.

© codexstar69, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/threat-model-generation of codexstar69/bug-hunter.

Open the folder on GitHubat commit 3be6973

Compare with similar skills

Threat Model Generation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Threat Model Generation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Threat Model Generation this skillcodexstar69/bug-hunter519—~408Automated safety check: PassMIT
Fla Ascend Performancefla-org/flash-linear-attention5.8k—~6.3kAutomated safety check: PassMIT
Forensifyalexgreensh/repo-forensics188—~2.5kAutomated safety check: NotesCustom licence
Create Rulecartography-cncf/cartography4.1k—~3kAutomated safety check: PassApache-2.0
Auditing Code For Vulnerabilitiestrilwu/secskills156—~3.2kAutomated safety check: PassMIT
Threat Mitigation Mappingwshobson/agents40k8 repos~742Automated safety check: PassMIT

Similar skills

  • Fla Ascend Performance

    fla-org/flash-linear-attention

    Guidelines for Ascend NPU kernel / Triton-Ascend backend performance work in the FLA repo.

    5.8k GitHub stars~6.3k tokensUpdated today
    SecurityAuto-check passed
  • Forensify

    alexgreensh/repo-forensics

    Cross-agent self-inspection of your AI-agent stack. An agent skill from alexgreensh/repo-forensics.

    188 GitHub stars~2.5k tokensUpdated 10 days ago
    SecurityAuto-check: notes
  • Create Rule

    cartography-cncf/cartography

    Author a Cartography security rule (one or more Cypher Facts plus a Pydantic Finding output model) under cartography/rules/data/rules/.

    4.1k GitHub stars~3k tokensUpdated today
    SecurityAuto-check passed
  • Audit source code for exploitable vulnerabilities using threat-model-driven review, taint tracing, invariant checking, and variant analysis.

    156 GitHub stars~3.2k tokensUpdated 1 mo ago
    SecurityAuto-check passed
  • Match identified threats to preventive, detective and corrective controls across network, application, data, endpoint and process layers to plan remediation.

    40k GitHub starsUsed in 8 repos~742 tokens
    SecurityAuto-check passed
  • Audit Browser Security Boundaries

    nordstjernen-web/northstar-browser

    Audit browser-engine changes that process untrusted content or cross native-memory, origin, network, storage, extension, decoder, sandbox, or operating-system boundaries.

    116 GitHub stars~920 tokensUpdated yesterday
    SecurityAuto-check passed

More from codexstar69/bug-hunter

All 11 skills in this repo
  • Bug Hunter

    codexstar69/bug-hunter

    Precision-first adversarial bug hunting for runtime, logic, data, concurrency, and security defects.

    519 GitHub stars~5k tokensUpdated 1 mo ago
    Auto-check passed
  • Commit Security Scan

    codexstar69/bug-hunter

    Scan code changes for security vulnerabilities using Bug Hunter-native artifacts and STRIDE context.

    519 GitHub stars~629 tokensUpdated 1 mo ago
    Auto-check passed
  • Doc Lookup

    codexstar69/bug-hunter

    Unified documentation lookup for Bug Hunter agents. An agent skill from codexstar69/bug-hunter.

    519 GitHub stars~592 tokensUpdated 1 mo ago
    Auto-check passed
  • Fixer

    codexstar69/bug-hunter

    Surgical code fixer for Bug Hunter. An agent skill from codexstar69/bug-hunter.

    519 GitHub stars~1.7k tokensUpdated 1 mo ago
    Auto-check passed
  • Hunter

    codexstar69/bug-hunter

    Deep behavioral code analysis agent for Bug Hunter. An agent skill from codexstar69/bug-hunter.

    519 GitHub stars~2.6k tokensUpdated 1 mo ago
    Auto-check passed
  • Recon

    codexstar69/bug-hunter

    Codebase reconnaissance agent for Bug Hunter. An agent skill from codexstar69/bug-hunter.

    519 GitHub stars~1.7k tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Threat Model Generation

What does Threat Model Generation do?

Generate or refresh a STRIDE-based threat model for the current repository using Bug Hunter-native artifacts. Threat Model Generation is an agent skill from codexstar69/bug-hunter. Generate or refresh a STRIDE-based threat model for the current repository using Bug Hunter-native artifacts.

When should I use Threat Model Generation?

Threat Model Generation fits situations like: the repository has no threat model yet; the architecture changed materially; A security review needs fresh trust-boundary context; the user explicitly asks for a threat model.

How do I install Threat Model Generation in Claude Code?

Run `npx skills add codexstar69/bug-hunter --skill threat-model-generation -a claude-code`. Or copy the skill folder (skills/threat-model-generation in codexstar69/bug-hunter) into .claude/skills/threat-model-generation in your project. Claude Code loads it when a task matches its description.

How do I install Threat Model Generation in Codex?

Run `npx skills add codexstar69/bug-hunter --skill threat-model-generation -a codex`. Or copy the skill folder (skills/threat-model-generation in codexstar69/bug-hunter) into .agents/skills/threat-model-generation in your project. Codex loads it when a task matches its description.

Can I use Threat Model Generation in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add codexstar69/bug-hunter --skill threat-model-generation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/threat-model-generation, .gemini/skills/threat-model-generation, .github/skills/threat-model-generation and .opencode/skills/threat-model-generation in your project.

What does Threat Model Generation need to run?

SKILL.md names no scripts, command-line tools or credentials: Threat Model Generation is instructions for the agent only.

Does Threat Model Generation access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Threat Model Generation safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Threat Model Generation use?

Threat Model Generation is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Threat Model Generation use?

About 408 tokens (SKILL.md is roughly 1.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Threat Model Generation?

Skills that share tags, products or a category with Threat Model Generation: Fla Ascend Performance (fla-org/flash-linear-attention, 5.8k stars), Forensify (alexgreensh/repo-forensics, 188 stars), Create Rule (cartography-cncf/cartography, 4.1k stars) and Auditing Code For Vulnerabilities (trilwu/secskills, 156 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Threat Model Generation?

codexstar69 (a GitHub user) maintains it in codexstar69/bug-hunter, which has 519 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on August 17, 2026.

Source: codexstar69/bug-hunter on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.