Forensify
alexgreensh/repo-forensics
Cross-agent self-inspection of your AI-agent stack. An agent skill from alexgreensh/repo-forensics.
Produce a repository-grounded application security threat model with assets, boundaries, abuse paths, priorities, and mitigations.
Install Repository Threat Model
$ npx skills add nightly-labs/openbot --skill repository-threat-model -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nightly-labs/openbot repository-threat-model --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/nightly-labs/openbot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/marketplace/production-catalog/skills/repository-threat-model .claude/skills/repository-threat-model && rm -rf skills-srcUse ~/.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/
Install the "repository-threat-model" agent skill from https://github.com/nightly-labs/openbot/tree/main/marketplace/production-catalog/skills/repository-threat-model into .claude/skills/repository-threat-model/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repository-threat-model", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/nightly-labs/openbot/tree/main/marketplace/production-catalog/skills/repository-threat-modelType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add nightly-labs/openbot --skill repository-threat-model -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nightly-labs/openbot repository-threat-model --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nightly-labs/openbot.git skills-src && mkdir -p .agents/skills && cp -r skills-src/marketplace/production-catalog/skills/repository-threat-model .agents/skills/repository-threat-model && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "repository-threat-model" agent skill from https://github.com/nightly-labs/openbot/tree/main/marketplace/production-catalog/skills/repository-threat-model into .agents/skills/repository-threat-model/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repository-threat-model", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nightly-labs/openbot --skill repository-threat-model -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nightly-labs/openbot repository-threat-model --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nightly-labs/openbot.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/marketplace/production-catalog/skills/repository-threat-model .cursor/skills/repository-threat-model && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "repository-threat-model" agent skill from https://github.com/nightly-labs/openbot/tree/main/marketplace/production-catalog/skills/repository-threat-model into .cursor/skills/repository-threat-model/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repository-threat-model", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/nightly-labs/openbot.git --path marketplace/production-catalog/skills/repository-threat-model--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add nightly-labs/openbot --skill repository-threat-model -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nightly-labs/openbot repository-threat-model --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nightly-labs/openbot.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/marketplace/production-catalog/skills/repository-threat-model .gemini/skills/repository-threat-model && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "repository-threat-model" agent skill from https://github.com/nightly-labs/openbot/tree/main/marketplace/production-catalog/skills/repository-threat-model into .gemini/skills/repository-threat-model/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repository-threat-model", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install nightly-labs/openbot repository-threat-modelInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add nightly-labs/openbot --skill repository-threat-model -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nightly-labs/openbot.git skills-src && mkdir -p .github/skills && cp -r skills-src/marketplace/production-catalog/skills/repository-threat-model .github/skills/repository-threat-model && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "repository-threat-model" agent skill from https://github.com/nightly-labs/openbot/tree/main/marketplace/production-catalog/skills/repository-threat-model into .github/skills/repository-threat-model/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repository-threat-model", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nightly-labs/openbot --skill repository-threat-model -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install nightly-labs/openbot repository-threat-model --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nightly-labs/openbot.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/marketplace/production-catalog/skills/repository-threat-model .opencode/skills/repository-threat-model && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "repository-threat-model" agent skill from https://github.com/nightly-labs/openbot/tree/main/marketplace/production-catalog/skills/repository-threat-model into .opencode/skills/repository-threat-model/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repository-threat-model", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
repository-threat-model- GitHub stars
- 489
- Token cost
- ~379 tokens
- SKILL.md length
- 166 words
- Files
- 1
- Skills in repo
- 15
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Produce a repository-grounded application security threat model with assets, boundaries, abuse paths, priorities, and mitigations.
- Tasks that involve Threat modeling
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Repository Threat Model is an agent skill from nightly-labs/openbot. Produce a repository-grounded application security threat model with assets, boundaries, abuse paths, priorities, and mitigations. Use only when threat modeling is explicitly requested.
Its SKILL.md is about 380 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: A local-first desktop workspace for persistent AI teammates. Run Codex, Claude, and Grok with dedicated workspaces, task queues, file sharing, browser control, and agent-to-agent…
When your agent uses it
- Tasks that involve Threat modeling
Example prompts
- “/repository-threat-model”
What it can do on your machine
Read from SKILL.md and the folder at commit c7d6ee9. 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
Repository Threat Model loads about 379 tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 166 words of instructions outside code blocks.
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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 166 words (~379 tokens).
“Build the model from repository evidence rather than a generic checklist. Establish the in-scope components, deployment assumptions, entry points, data stores, external integrations, and trust boundaries. Separate runtime behavior from development and CI tooling.”
- name
- repository-threat-model
Files
Just SKILL.md in marketplace/production-catalog/skills/repository-threat-model of nightly-labs/openbot.
Open the folder on GitHubat commit c7d6ee9
Compare with similar skills
Repository Threat Model 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Repository Threat Model this skillnightly-labs/openbot | 489 | — | ~379 | Automated safety check: Pass | Custom licence | |
| Forensifyalexgreensh/repo-forensics | 190 | — | ~2.5k | Automated safety check: Notes | Custom licence | |
| Create Rulecartography-cncf/cartography | 4.1k | — | ~3k | Automated safety check: Pass | Apache-2.0 | |
| Commit Security Scancodexstar69/bug-hunter | 520 | — | ~629 | Automated safety check: Pass | MIT | |
| Auditing Code For Vulnerabilitiestrilwu/secskills | 157 | — | ~3.2k | Automated safety check: Pass | MIT | |
| Threat Mitigation Mappingwshobson/agents | 40k | 8 repos | ~742 | Automated safety check: Pass | MIT |
Similar skills
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/.
Commit Security Scan
codexstar69/bug-hunter
Scan code changes for security vulnerabilities using Bug Hunter-native artifacts and STRIDE context.
Auditing Code For Vulnerabilities
trilwu/secskills
Audit source code for exploitable vulnerabilities using threat-model-driven review, taint tracing, invariant checking, and variant analysis.
Threat Mitigation Mapping
wshobson/agents
Match identified threats to preventive, detective and corrective controls across network, application, data, endpoint and process layers to plan remediation.
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.
More from nightly-labs/openbot
All 15 skills in this repoBiome Anti Slop
nightly-labs/openbot
Install and configure vendored Biome anti-slop GritQL rules in a local TypeScript or JavaScript repository.
Release Upgrade Safety
nightly-labs/openbot
Audit a pending OpenBot release for upgrade and data-loss hazards before the version is bumped or tagged.
Babysit
nightly-labs/openbot
Babysit a pull request through the NorbiAI review loop until no valid issue remains.
Openbot Export
nightly-labs/openbot
Export the user's Grok Bot agents into one .zip file that OpenBot imports, with instructions, avatars, skills, routines, memories, group chats, and optional workspace files.
Ship
nightly-labs/openbot
Ship the current branch to main. An agent skill from nightly-labs/openbot.
Signal Deploy
nightly-labs/openbot
Check and deploy Signal (the remote-api service in remote/) to production from a release tag.
Related
Categories
Questions about Repository Threat Model
What does Repository Threat Model do?
Produce a repository-grounded application security threat model with assets, boundaries, abuse paths, priorities, and mitigations. Repository Threat Model is an agent skill from nightly-labs/openbot. Produce a repository-grounded application security threat model with assets, boundaries, abuse paths, priorities, and mitigations.
When should I use Repository Threat Model?
Repository Threat Model fits situations like: tasks that involve Threat modeling.
How do I install Repository Threat Model in Claude Code?
Run `npx skills add nightly-labs/openbot --skill repository-threat-model -a claude-code`. Or copy the skill folder (marketplace/production-catalog/skills/repository-threat-model in nightly-labs/openbot) into .claude/skills/repository-threat-model in your project. Claude Code loads it when a task matches its description.
How do I install Repository Threat Model in Codex?
Run `npx skills add nightly-labs/openbot --skill repository-threat-model -a codex`. Or copy the skill folder (marketplace/production-catalog/skills/repository-threat-model in nightly-labs/openbot) into .agents/skills/repository-threat-model in your project. Codex loads it when a task matches its description.
Can I use Repository Threat Model 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 nightly-labs/openbot --skill repository-threat-model -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/repository-threat-model, .gemini/skills/repository-threat-model, .github/skills/repository-threat-model and .opencode/skills/repository-threat-model in your project.
What does Repository Threat Model need to run?
SKILL.md names no scripts, command-line tools or credentials: Repository Threat Model is instructions for the agent only.
Does Repository Threat Model 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 Repository Threat Model 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 Repository Threat Model use?
Repository Threat Model has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Repository Threat Model use?
About 379 tokens (SKILL.md is roughly 1.5k 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 Repository Threat Model?
Skills that share tags, products or a category with Repository Threat Model: Forensify (alexgreensh/repo-forensics, 190 stars), Create Rule (cartography-cncf/cartography, 4.1k stars), Commit Security Scan (codexstar69/bug-hunter, 520 stars) and Auditing Code For Vulnerabilities (trilwu/secskills, 157 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Repository Threat Model?
nightly-labs (a GitHub organization) maintains it in nightly-labs/openbot, which has 489 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 9, 2026.
Source: nightly-labs/openbot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.