security-review

A code-security review that checks changed files for vulnerabilities, including common OWASP Top 10 risks and problems tied to the project's technology stack.

In plain words
What is it for?
Use it to review a branch or set of changed files for security issues in areas such as login, payments, file handling, and real-time features.
Why use it?
It helps find security problems before changed code is merged or released, and turns the findings into a self-contained worklist.

Skill for Claude CodeCodex

Part of the docx-cli plugin — 4 skills, 1 agent shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/kklimuk/docx-cli/security-review
Any agent
npx skills add kklimuk/docx-cli --skill security-review
Clone the repo
git clone --depth 1 https://github.com/kklimuk/docx-cli

Made for: Claude Code, Codex.

Or install docx-cli, the plugin that ships this one along with the rest of its 4 skills, 1 agent.

Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,501 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00047 $0.01501
Opus 5 $0.00023 $0.00750
Sonnet 5 $0.00009 $0.00300
Haiku 4.5 $0.00005 $0.00150

Measured 3d ago against content hash 149ce84bfad5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

security-review scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

- **Command injection**: User input passed to shell commands (`Bun.$`, `child_process`, `subprocess`, `os.system`) without sanitization.
.claude/skills/security-review/SKILL.md · 112 lines

How it starts

The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Security Review

Audit changed files for security vulnerabilities, focusing on the OWASP Top 10 and issues specific to the project's stack.

When running locally as a forked subagent, the main session does not see any files you read or any reasoning you do — only the final report you return. When running in CI (e.g. via claude-code-action), the workflow takes the report and turns it into GitHub PR review comments. Either way, take your time, read every changed file completely, and produce a thorough, actionable report. The consumer of this report uses it as a worklist, so it must be complete and self-contained.

Scope

Determine the diff to review:

  1. Run git diff main...HEAD --name-only to get files changed on this branch vs main.
  2. If that fails (no main, detached worktree, etc.), fall back to git diff HEAD --name-only for uncommitted changes, then git diff --cached --name-only for staged files.
  3. If no diff is available, ask the user which files to review.

Read every changed file completely before starting the review. Read CLAUDE.md first to understand the project's stack and any subsystems with security-sensitive surface area (auth, real-time, payments, file uploads).

What to Look For

Injection & Input Handling

  • SQL injection: Raw SQL with string interpolation instead of parameterized queries. Check for any template literals that build SQL, and verify that database libraries are being used in their parameterized form.
  • Command injection: User input passed to shell commands (Bun.$, child_process, subprocess, os.system) without sanitization.
  • XSS: User-controlled data rendered as dangerouslySetInnerHTML, or reflected into HTML/JS without escaping. Check contentEditable fields that accept pasted HTML.
  • Path traversal: User input used in file paths without validation. Check for .. traversal.
  • Prototype pollution: Object.assign or spread on user-controlled objects without allowlisting keys.

Authentication & Authorization

Read the full file on GitHub · 112 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 112 lines · 47 tokens per session scan A 149ce84bfad5

Subscribe to this mod's changes

security-review is a skill published in the GitHub repository kklimuk/docx-cli (194 stars, last pushed 16d ago), licensed MIT. It adds 47 tokens to every session and 1,501 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

vox-director

Turn ONE topic into a finished Vox-style paper-collage explainer / ad video, end to end on the Atlas Cloud API + local ffmpeg — script, collage keyframes, motion, voice-over, music, captions, all automated. Use this whenever the user wants a "Vox style" video, a paper/torn-paper collage animation, a "motion collage"…

Alisa0808/vox-director · 236 tokens

social-post

學習使用者的 Facebook/Instagram/YouTube/Threads/X 語氣與受眾,規劃、撰寫、確認後發佈內容;以已登入 Chrome 受控掃描、草擬及回覆 FB/IG/Threads 留言;並作為流量、留存與轉化的結構化帳本。使用者說「發文」「用我的口氣」「回覆留言」「自動回留言」「掃留言」「查流量」「演算法」「把數據訓練進去」「比較貼文」「優化 pattern」時使用。.

Hao0321/claude-skill-social-post · 135 tokens

privacy-eu

EU 사용자 대상 서비스용 Privacy Notice·Terms of Service·Consent Modal·Cookie Banner 자동 생성. GDPR (Regulation 2016/679) + ePrivacy Directive + Consumer Rights Directive 2011/83 + Digital Services Act + Digital Content Directive + Unfair Terms Directive 반영. 영문 인터뷰로 진행.

kimlawtech/korean-privacy-terms · 70 tokens

privacy-terms

처리방침·이용약관 자동 생성 진입점. 호출 즉시 6개 하위 스킬(privacy-kr·privacy-eu·privacy-us·privacy-jp·privacy-global·privacy-global-jp)을 번호 메뉴로 제시하고, 번호 입력 즉시 해당 스킬 인터뷰로 직행한다.

kimlawtech/korean-privacy-terms · 74 tokens

higgsfield-troubleshoot

Use when a Higgsfield generation fails, produces poor quality, looks wrong, doesn't match the prompt, or the user needs to fix or improve an output.

OSideMedia/higgsfield-ai-prompt-skill · 39 tokens

higgsfield-motion-design

End-to-end motion-design / animated-ad creation flow on Higgsfield via the MCP connector. Use when the user wants to create motion design, animate a logo, make a video from an image, build an animated ad or brand promo, turn a product into motion, or says 'make a motion', 'motion design', 'animate this', 'make a video…

OSideMedia/higgsfield-ai-prompt-skill · 199 tokens