Security Review
jewbetcha/opentrace
A skill your agent uses when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features.
AI-powered security vulnerability detection. An agent skill from selmakcby/claude-agents-skills.
Install Security Review
$ npx skills add selmakcby/claude-agents-skills --skill security-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install selmakcby/claude-agents-skills security-review --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/selmakcby/claude-agents-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/my-project-demo/.claude/skills/security-review .claude/skills/security-review && 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 "security-review" agent skill from https://github.com/selmakcby/claude-agents-skills/tree/main/my-project-demo/.claude/skills/security-review into .claude/skills/security-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-review", 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/selmakcby/claude-agents-skills/tree/main/my-project-demo/.claude/skills/security-reviewType 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 selmakcby/claude-agents-skills --skill security-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install selmakcby/claude-agents-skills security-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/selmakcby/claude-agents-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/my-project-demo/.claude/skills/security-review .agents/skills/security-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "security-review" agent skill from https://github.com/selmakcby/claude-agents-skills/tree/main/my-project-demo/.claude/skills/security-review into .agents/skills/security-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-review", 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 selmakcby/claude-agents-skills --skill security-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install selmakcby/claude-agents-skills security-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/selmakcby/claude-agents-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/my-project-demo/.claude/skills/security-review .cursor/skills/security-review && 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 "security-review" agent skill from https://github.com/selmakcby/claude-agents-skills/tree/main/my-project-demo/.claude/skills/security-review into .cursor/skills/security-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-review", 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/selmakcby/claude-agents-skills.git --path my-project-demo/.claude/skills/security-review--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 selmakcby/claude-agents-skills --skill security-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install selmakcby/claude-agents-skills security-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/selmakcby/claude-agents-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/my-project-demo/.claude/skills/security-review .gemini/skills/security-review && 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 "security-review" agent skill from https://github.com/selmakcby/claude-agents-skills/tree/main/my-project-demo/.claude/skills/security-review into .gemini/skills/security-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-review", 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 selmakcby/claude-agents-skills security-reviewInstalls 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 selmakcby/claude-agents-skills --skill security-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/selmakcby/claude-agents-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/my-project-demo/.claude/skills/security-review .github/skills/security-review && 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 "security-review" agent skill from https://github.com/selmakcby/claude-agents-skills/tree/main/my-project-demo/.claude/skills/security-review into .github/skills/security-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-review", 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 selmakcby/claude-agents-skills --skill security-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install selmakcby/claude-agents-skills security-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/selmakcby/claude-agents-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/my-project-demo/.claude/skills/security-review .opencode/skills/security-review && 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 "security-review" agent skill from https://github.com/selmakcby/claude-agents-skills/tree/main/my-project-demo/.claude/skills/security-review into .opencode/skills/security-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-review", 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
security-review- GitHub stars
- 136
- Token cost
- ~963 tokens
- SKILL.md length
- 394 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- MIT
At a glance
AI-powered security vulnerability detection. An agent skill from selmakcby/claude-agents-skills.
- Works in 10 steps: Injection → Broken authentication → Sensitive data exposure → …
- Tasks that involve Web application vulnerabilities
- SKILL.md covers When to trigger, Scanning mode, What to check (OWASP Top 10… and AI-specific checks, plus 3 more sections
- Calls npm
What it does
Security Review is an agent skill from selmakcby/claude-agents-skills. AI-powered security vulnerability detection. Use PROACTIVELY after writing code that handles user input, authentication, API endpoints, payments, or sensitive data. Flags OWASP Top 10 issues with diff-aware scanning.
Its SKILL.md is about 960 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 Web application vulnerabilities, Security review and REST APIs. The repository describes itself as: Multi-Agent Claude Code setup — 4 uzman ajan (planner · ui-agent · builder · reviewer) + skills + Next.js demo projesi. YouTube Bölüm 1 video materyalleri. The licence is MIT.
When your agent uses it
- Tasks that involve Web application vulnerabilities
- Tasks that involve Security review
- Tasks that involve REST APIs
Example prompts
- “/security-review”
Workflow steps
10 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit ddcfb0c. 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:
npm
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):
github.com
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
Security Review loads about 963 tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 394 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
The full file from selmakcby/claude-agents-skills at commit ddcfb0c, republished under its MIT licence (© selmakcby). 394 words, ~963 tokens.
Download SKILL.mdSave it as
.claude/skills/security-review/SKILL.md (or your agent's skills folder).- name
- security-review
- description
- AI-powered security vulnerability detection. Use PROACTIVELY after writing code that handles user input, authentication, API endpoints, payments, or sensitive data. Flags OWASP Top 10 issues with diff-aware scanning.
<!--
Source: anthropics/claude-code-security-review (official)
File: https://github.com/anthropics/claude-code-security-review/blob/main/.claude/commands/security-review.md
Used by: reviewer agent
-->Security Review
When to trigger
- After writing code touching auth, payments, API endpoints, file I/O, or user input
- Before commit on security-sensitive changes
- When user asks
/security-review
Scanning mode
Diff-aware: only analyze changed files in the current PR/commit. Focus on real vulnerabilities — filter out false positives aggressively.
What to check (OWASP Top 10 mapping)
1. Injection
- SQL injection → parameterized queries?
- NoSQL injection → $where clauses, user-controlled operators?
- Command injection →
exec()with user input? - Prompt injection (AI-specific) → user input flowing into system prompts?
2. Broken authentication
- Missing auth checks on protected routes
- Weak password hashing (bcrypt/argon2 required)
- JWT misuse — missing signature verification, weak secrets,
nonealgorithm accepted - Session fixation, missing session rotation on login
3. Sensitive data exposure
- Hardcoded secrets in code
- API keys in client bundles (import in
"use client"components) - PII in logs
- Missing HTTPS enforcement
- Secrets in error messages
4. XML/XXE
- XML parsers with external entity processing enabled
5. Broken access control
- Missing authorization (authenticated but not authorized)
- IDOR (accessing other users' data by changing an ID)
- Privilege escalation paths
6. Security misconfiguration
- Default credentials
- Debug endpoints exposed in prod
- Missing security headers (CSP, HSTS, X-Frame-Options)
7. XSS
dangerouslySetInnerHTMLwith user input- Rendering LLM output without sanitization
- URL parameters reflected without escaping
8. Insecure deserialization
JSON.parsewith user-controlled content (usually fine in JS, but watch for prototype pollution)
9. Using components with known vulnerabilities
- Run
npm auditmentally — are any flagged deps in critical paths?
Show full SKILL.md (158 more words)Show less
10. Insufficient logging
- Security events unlogged (failed logins, permission denials)
- Overlogging (logging PII, tokens, passwords)
AI-specific checks
- Webhooks: signature verification present? (Stripe, GitHub, etc.)
- Rate limiting: on public endpoints? On AI endpoints especially?
- Input length: max length on LLM inputs?
- Output validation: Zod schema on LLM responses before rendering?
- CORS / CSRF: properly configured for auth endpoints?
Severity (same as code-review)
- CRITICAL — exposed secret, missing auth, unverified webhook, SQL injection, missing rate limit on AI endpoint
- HIGH — missing input validation, weak crypto
- MEDIUM — logging gaps, overly verbose errors
- LOW — defense-in-depth suggestions
Output format
## CRITICAL
- [`<file>:<line>`] <vulnerability> (OWASP: <category>)
- Impact: <what an attacker could do>
- Fix: <specific mitigation>
## HIGH / MEDIUM / LOW
- ...
## Verdict
PASS | BLOCK (CRITICAL count: N)Rules
- Never hand-wave. "This might be a risk" is not enough — say if it is or isn't, with evidence.
- Every finding: severity, OWASP category, file + line, attacker scenario, specific fix.
- Rotate suspected exposed secrets immediately and flag at top of report.
- False positives are worse than no review — if you're not sure, don't flag it.
- AI endpoints get extra scrutiny — token limits, output sanitization, rate limits.
© selmakcby, 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 my-project-demo/.claude/skills/security-review of selmakcby/claude-agents-skills.
Open the folder on GitHubat commit ddcfb0c
Compare with similar skills
Security Review 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 |
|---|---|---|---|---|---|---|
| Security Review this skillselmakcby/claude-agents-skills | 136 | — | ~963 | Automated safety check: Pass | MIT | |
| Security Reviewjewbetcha/opentrace | 116 | 18 repos | ~3.1k | Automated safety check: Notes | MIT | |
| Security Reviewaffaan-m/ECC | 276k | 1 repos | ~3.2k | Automated safety check: Notes | MIT | |
| Security Auditoreigent-ai/eigent | 15k | — | ~1.8k | Automated safety check: Notes | Apache-2.0 | |
| Strix Code Vulnerability Scanusestrix/strix | 68k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Code Audit3stoneBrother/code-audit | 892 | 1 repos | ~2.7k | Automated safety check: Pass | None |
Similar skills
Security Review
affaan-m/ECC
Kimlik doğrulama eklerken, kullanıcı girdisi işlerken, secret'larla çalışırken, API endpoint'leri oluştururken veya ödeme/hassas özellikler uygularken bu skill'i kullanın.
Security Auditor
eigent-ai/eigent
Audits source code, dependencies and config files for vulnerabilities and hardcoded secrets, using two bundled Python scanners and an OWASP Top 10 checklist.
Strix Code Vulnerability Scan
usestrix/strix
Runs a Strix white-box security review that reads the source, then exploits what it finds in a sandbox so each reported issue has a proof-of-concept.
Code Audit
3stoneBrother/code-audit
Professional code security audit skill covering 55+ vulnerability types.
Wooyun Legacy
tanweai/wooyun-legacy
WooYun business logic vulnerability methodology — 22,132 real cases across 6 domains (authentication bypass, authorization bypass, payment tampering, information disclosure, logic flaws…
More from selmakcby/claude-agents-skills
All 8 skills in this repoAPI Design
selmakcby/claude-agents-skills
Backend API design specialist. An agent skill from selmakcby/claude-agents-skills.
Plan
selmakcby/claude-agents-skills
Implementation planning specialist. An agent skill from selmakcby/claude-agents-skills.
UI UX Pro Max
selmakcby/claude-agents-skills
UI/UX design intelligence for web and mobile. An agent skill from selmakcby/claude-agents-skills.
UI UX Pro Max
selmakcby/claude-agents-skills
UI/UX design intelligence. An agent skill from selmakcby/claude-agents-skills.
Code Review
selmakcby/claude-agents-skills
Senior code review specialist. An agent skill from selmakcby/claude-agents-skills.
Code Review
selmakcby/claude-agents-skills
Senior code review specialist. An agent skill from selmakcby/claude-agents-skills.
Related
Categories
Questions about Security Review
What does Security Review do?
AI-powered security vulnerability detection. An agent skill from selmakcby/claude-agents-skills. Security Review is an agent skill from selmakcby/claude-agents-skills. AI-powered security vulnerability detection.
When should I use Security Review?
Security Review fits situations like: tasks that involve Web application vulnerabilities; tasks that involve Security review; tasks that involve REST APIs.
How do I install Security Review in Claude Code?
Run `npx skills add selmakcby/claude-agents-skills --skill security-review -a claude-code`. Or copy the skill folder (my-project-demo/.claude/skills/security-review in selmakcby/claude-agents-skills) into .claude/skills/security-review in your project. Claude Code loads it when a task matches its description.
How do I install Security Review in Codex?
Run `npx skills add selmakcby/claude-agents-skills --skill security-review -a codex`. Or copy the skill folder (my-project-demo/.claude/skills/security-review in selmakcby/claude-agents-skills) into .agents/skills/security-review in your project. Codex loads it when a task matches its description.
Can I use Security Review 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 selmakcby/claude-agents-skills --skill security-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/security-review, .gemini/skills/security-review, .github/skills/security-review and .opencode/skills/security-review in your project.
What does Security Review need to run?
Going by SKILL.md and its folder, Security Review needs the command-line tools its instructions call (npm).
Does Security Review access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Security Review 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 Security Review use?
Security Review 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 Security Review use?
About 963 tokens (SKILL.md is roughly 3.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 Security Review?
Skills that share tags, products or a category with Security Review: Security Review (jewbetcha/opentrace, 116 stars), Security Review (affaan-m/ECC, 276k stars), Security Auditor (eigent-ai/eigent, 15k stars) and Strix Code Vulnerability Scan (usestrix/strix, 68k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Security Review?
selmakcby (a GitHub user) maintains it in selmakcby/claude-agents-skills, which has 136 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on April 21, 2026.
Source: selmakcby/claude-agents-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.