Levyra Security Review
LUC4N3X/Levyra-deepsound
Perform an evidence-based Levyra security review and Codex Security workflow covering threat modeling, attack paths, validation, remediation, revalidation, secrets, provider URLs, redirects, SSRF…
Analyze code changes for security vulnerabilities using LLM reasoning and threat model patterns.
Install Commit Security Scan
$ npx skills add Factory-AI/factory-plugins --skill commit-security-scan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Factory-AI/factory-plugins commit-security-scan --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/Factory-AI/factory-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/security-engineer/skills/commit-security-scan .claude/skills/commit-security-scan && 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 "commit-security-scan" agent skill from https://github.com/Factory-AI/factory-plugins/tree/master/plugins/security-engineer/skills/commit-security-scan into .claude/skills/commit-security-scan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-security-scan", 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/Factory-AI/factory-plugins/tree/master/plugins/security-engineer/skills/commit-security-scanType 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 Factory-AI/factory-plugins --skill commit-security-scan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Factory-AI/factory-plugins commit-security-scan --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Factory-AI/factory-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/security-engineer/skills/commit-security-scan .agents/skills/commit-security-scan && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "commit-security-scan" agent skill from https://github.com/Factory-AI/factory-plugins/tree/master/plugins/security-engineer/skills/commit-security-scan into .agents/skills/commit-security-scan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-security-scan", 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 Factory-AI/factory-plugins --skill commit-security-scan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Factory-AI/factory-plugins commit-security-scan --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Factory-AI/factory-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/security-engineer/skills/commit-security-scan .cursor/skills/commit-security-scan && 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 "commit-security-scan" agent skill from https://github.com/Factory-AI/factory-plugins/tree/master/plugins/security-engineer/skills/commit-security-scan into .cursor/skills/commit-security-scan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-security-scan", 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/Factory-AI/factory-plugins.git --path plugins/security-engineer/skills/commit-security-scan--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 Factory-AI/factory-plugins --skill commit-security-scan -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Factory-AI/factory-plugins commit-security-scan --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Factory-AI/factory-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/security-engineer/skills/commit-security-scan .gemini/skills/commit-security-scan && 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 "commit-security-scan" agent skill from https://github.com/Factory-AI/factory-plugins/tree/master/plugins/security-engineer/skills/commit-security-scan into .gemini/skills/commit-security-scan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-security-scan", 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 Factory-AI/factory-plugins commit-security-scanInstalls 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 Factory-AI/factory-plugins --skill commit-security-scan -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Factory-AI/factory-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/security-engineer/skills/commit-security-scan .github/skills/commit-security-scan && 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 "commit-security-scan" agent skill from https://github.com/Factory-AI/factory-plugins/tree/master/plugins/security-engineer/skills/commit-security-scan into .github/skills/commit-security-scan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-security-scan", 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 Factory-AI/factory-plugins --skill commit-security-scan -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Factory-AI/factory-plugins commit-security-scan --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Factory-AI/factory-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/security-engineer/skills/commit-security-scan .opencode/skills/commit-security-scan && 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 "commit-security-scan" agent skill from https://github.com/Factory-AI/factory-plugins/tree/master/plugins/security-engineer/skills/commit-security-scan into .opencode/skills/commit-security-scan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-security-scan", 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
commit-security-scan- GitHub stars
- 110
- Token cost
- ~2.3k tokens
- SKILL.md length
- 845 words
- Files
- 2
- Skills in repo
- 13
- Repo updated
- First seen
- Licence
- None found
At a glance
Analyze code changes for security vulnerabilities using LLM reasoning and threat model patterns.
- Works in 7 steps: Verify Prerequisites (Auto-Generate if… → Get Changed Files → Load Threat Model → …
- Pre-commit checks
- SKILL.md covers When to Use This Skill, Prerequisites, Inputs and Instructions, plus 3 more sections
- Calls git and gh
What it does
Commit Security Scan is an agent skill from Factory-AI/factory-plugins. Analyze code changes for security vulnerabilities using LLM reasoning and threat model patterns. Use for PR reviews, pre-commit checks, or branch comparisons.
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `analysis-examples.md`).
It sits in Security, covering Security review, Threat modeling and Pull requests. The repository describes itself as: Official Factory plugins marketplace.
When your agent uses it
- Pre-commit checks
- Branch comparisons
Example prompts
- “/commit-security-scan”
Workflow steps
7 steps, taken from the step headings in SKILL.md.
- Verify Prerequisites (Auto-Generate if Missing)
- Get Changed Files
- Load Threat Model
- Analyze for Vulnerabilities
- Assess Each Finding
- Generate Report
- Report Results
What it can do on your machine
Read from SKILL.md and the folder at commit d362dc1. 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
Shell commands in SKILL.md call:
gitgh
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
owasp.orgcwe.mitre.org
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
Commit Security Scan loads about 2.3k tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 845 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
Without a licence we can't republish the file, so here is its outline and opening line. It has 845 words (~2,253 tokens).
“Analyze code changes (commits, PRs, diffs) using LLM-powered reasoning to detect security vulnerabilities. This skill reads code directly and applies patterns from the repository's threat model to identify issues across all STRIDE categories.”
- name
- commit-security-scan
- version
- 1.0.0
- tags
- security, scanning, vulnerability-detection, ci-cd
Files
SKILL.md and 1 other file in plugins/security-engineer/skills/commit-security-scan of Factory-AI/factory-plugins.
- SKILL.md
- analysis-examples.md
Open the folder on GitHubat commit d362dc1
Compare with similar skills
Commit Security Scan 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 |
|---|---|---|---|---|---|---|
| Commit Security Scan this skillFactory-AI/factory-plugins | 110 | — | ~2.3k | Automated safety check: Pass | None | |
| Levyra Security ReviewLUC4N3X/Levyra-deepsound | 543 | — | ~2.3k | Automated safety check: Pass | GPL-3.0 | |
| GitHub Actions Hardeninggithub/awesome-copilot | 40k | 1 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Commit Security Scancodexstar69/bug-hunter | 519 | — | ~629 | Automated safety check: Pass | MIT | |
| Auditing Code For Vulnerabilitiestrilwu/secskills | 156 | — | ~3.2k | Automated safety check: Pass | MIT | |
| Audit Browser Security Boundariesnordstjernen-web/northstar-browser | 112 | — | ~920 | Automated safety check: Pass | GPL-3.0 |
Similar skills
- Official
GitHub Actions Hardening
github/awesome-copilot
Security hardening reviewer for GitHub Actions workflow files (.github/workflows/.yml).
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.
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.
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.
More from Factory-AI/factory-plugins
All 13 skills in this repoAutoresearch
Factory-AI/factory-plugins
Autonomous experiment loop for optimization research. An agent skill from Factory-AI/factory-plugins.
Ban Type Assertions
Factory-AI/factory-plugins
Ban as type assertions in a package via the @typescript-eslint/consistent-type-assertions lint rule, replacing them with compiler-verified type-safe alternatives.
Browser Navigation
Factory-AI/factory-plugins
Automate browser interactions for web testing, form filling, screenshots, and data extraction.
Create PR
Factory-AI/factory-plugins
Create a pull request with Conventional Commits formatting, a templated body, and local verification.
Droid Control
Factory-AI/factory-plugins
Control terminal TUIs, browsers, and native desktop apps for testing, demos, QA, and computer-use tasks.
Fix Knip Unused Exports
Factory-AI/factory-plugins
Fix knip "Unused exports" violations. An agent skill from Factory-AI/factory-plugins.
Related
Categories
Questions about Commit Security Scan
What does Commit Security Scan do?
Analyze code changes for security vulnerabilities using LLM reasoning and threat model patterns. Commit Security Scan is an agent skill from Factory-AI/factory-plugins. Analyze code changes for security vulnerabilities using LLM reasoning and threat model patterns.
When should I use Commit Security Scan?
Commit Security Scan fits situations like: pre-commit checks; branch comparisons.
How do I install Commit Security Scan in Claude Code?
Run `npx skills add Factory-AI/factory-plugins --skill commit-security-scan -a claude-code`. Or copy the skill folder (plugins/security-engineer/skills/commit-security-scan in Factory-AI/factory-plugins) into .claude/skills/commit-security-scan in your project. Claude Code loads it when a task matches its description.
How do I install Commit Security Scan in Codex?
Run `npx skills add Factory-AI/factory-plugins --skill commit-security-scan -a codex`. Or copy the skill folder (plugins/security-engineer/skills/commit-security-scan in Factory-AI/factory-plugins) into .agents/skills/commit-security-scan in your project. Codex loads it when a task matches its description.
Can I use Commit Security Scan 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 Factory-AI/factory-plugins --skill commit-security-scan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/commit-security-scan, .gemini/skills/commit-security-scan, .github/skills/commit-security-scan and .opencode/skills/commit-security-scan in your project.
What does Commit Security Scan need to run?
Going by SKILL.md and its folder, Commit Security Scan needs the command-line tools its instructions call (git and gh).
Does Commit Security Scan access the network?
SKILL.md names 2 domains. As links in the text: owasp.org and cwe.mitre.org. This is read from the text; nothing was executed.
Is Commit Security Scan 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 Commit Security Scan use?
No licence was found for Commit Security Scan or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Commit Security Scan use?
About 2.3k tokens (SKILL.md is roughly 9k 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 Commit Security Scan?
Skills that share tags, products or a category with Commit Security Scan: Levyra Security Review (LUC4N3X/Levyra-deepsound, 543 stars), GitHub Actions Hardening (github/awesome-copilot, 40k stars), Commit Security Scan (codexstar69/bug-hunter, 519 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 Commit Security Scan?
Factory-AI (a GitHub organization) maintains it in Factory-AI/factory-plugins, which has 110 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on September 15, 2026.
Source: Factory-AI/factory-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.