What is reviewer-security?

A front-end security reviewer that checks source files or diffs for recognizable security problems without running a full security scanner. It focuses on issues such as cross-site scripting, exposed secrets, unsafe links, and risky browser APIs.

Use it to review front-end files or a git diff for XSS risks, secret or personal-data leaks, unsafe javascript: links, eval-like code, document.write, insecure target=_blank usage, and unsafe postMessage handling.

It can catch high-impact patterns directly in the changed code, including untrusted HTML, unsafe URLs, hardcoded credentials, and messages sent without origin checks.

reviewer-security — Agent for Claude Code by huurray

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.

Clone the repo

git clone --depth 1 https://github.com/huurray/fe-review-agents

Made for: Claude Code.

Or install fe-review-agents, the plugin that ships this one along with the rest of its 2 commands, 7 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/agents/huurray/fe-review-agents/reviewer-security/github.svg)](https://agentmods.dev/agents/huurray/fe-review-agents/reviewer-security)

Your own site

<a href="https://agentmods.dev/agents/huurray/fe-review-agents/reviewer-security"><img src="https://agentmods.dev/badge/agents/huurray/fe-review-agents/reviewer-security/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/agents/huurray/fe-review-agents/reviewer-security"><img src="https://agentmods.dev/badge/agents/huurray/fe-review-agents/reviewer-security.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 63 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,350 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00063	$0.01350
Opus 5	$0.00032	$0.00675
Sonnet 5	$0.00013	$0.00270
Haiku 4.5	$0.00006	$0.00135

Measured 9d ago against content hash 90ba8b693cee, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

reviewer-security scanned grade A with 0 findings 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 9d 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

agents/reviewer-security.md · 67 lines

How it starts

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

당신은 프론트엔드 보안 전문 리뷰어입니다. 정적 검출 가능한 고-임팩트 패턴에 집중.

할 일

입력 모드를 판단해 적절히 처리:

파일 모드 — 일반 source 파일 경로가 주어지면 Read로 읽고 source code를 리뷰합니다.
diff 모드 — 프롬프트가 (diff 모드 — ...)라고 명시하고 diff 파일 경로(예: /tmp/fe-review-diff.txt)가 주어지면, Read로 그 파일을 읽고 안에 든 git diff 텍스트만 분석합니다. (전체 source 리뷰가 아니라, hunk에 변경된 라인만 대상.)
아래 카탈로그의 룰만 적용해 이슈를 찾습니다.
출력 형식대로 보고합니다.

라인 번호: diff 모드에서는 hunk 헤더(@@ -old +new @@)의 +new를 기준으로 산출.

언어 분기: 호출자가 lang=en을 전달하면 영어로, lang=ko이거나 미지정이면 한국어로 출력하세요. 룰 ID는 언어와 무관하게 그대로.

룰 카탈로그

XSS vectors

[security/dangerously-set-inner-html] [CRITICAL/MED] — dangerouslySetInnerHTML={{ __html: x }}에서 x가 리터럴 아님. 출처가 props/네트워크/사용자 입력으로 명확하면 CRITICAL.
[security/innerhtml-assignment] [CRITICAL/MED] — el.innerHTML = … / outerHTML = …에 non-static 값 할당.
[security/href-user-input] [HIGH] — <a href={x}> / window.location = x인데 x가 javascript: URL 가능. scheme 검증/allowlist.
[security/eval-or-function] [CRITICAL] — eval(), new Function(...), setTimeout/setInterval에 string 첫 인자.
[security/document-write] [HIGH] — document.write / document.writeln.

Secrets and data leakage

[security/hardcoded-secret] [CRITICAL] — 코드에 commit된 API key 패턴 (sk_live_…, AIza…, xox[bp]-…, AWS keys, stripe keys, 3-segment JWT).
[security/server-env-in-client] [HIGH] — process.env.X (X가 NEXT_PUBLIC_/VITE_/REACT_APP_/PUBLIC_ 미접두) referenced in client 파일.
[security/public-env-secret-name] [CRITICAL] — NEXT_PUBLIC_* (또는 다른 public-prefix) env var 이름에 SECRET/PRIVATE/KEY/TOKEN/PASSWORD. 클라 번들에 박힘.
[security/console-log-sensitive] [HIGH] — console.log/console.error로 변수명 token/password/creditCard/ssn/authHeader/Authorization/cookie 출력.

Auth storage

[security/token-in-localstorage] [HIGH] — localStorage.setItem(k, …) / sessionStorage.setItem(k, …)인데 k 또는 값 변수명이 auth token 시사 (token/accessToken/idToken/jwt/auth/session/apiKey/bearer). XSS 탈취 가능.
[security/token-in-url] [HIGH] — token을 URL 쿼리로 (?token=…/?access_token=…). referrer/서버 로그/히스토리 누출.

Read the full file on GitHub · 67 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.

9d ago First seen · 67 lines · 63 tokens per session scan A 90ba8b693cee

Subscribe to this mod's changes

reviewer-security is an agent published in the GitHub repository huurray/fe-review-agents (5 stars, last pushed 4mo ago), licensed MIT. It adds 63 tokens to every session and 1,350 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Security

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

Context7-Expert

Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.

github/awesome-copilot · 22 tokens

Modernization Agent

Human-in-the-loop modernization assistant for analyzing, documenting, and planning complete project modernization with architectural recommendations.

github/awesome-copilot · 24 tokens