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.
git clone --depth 1 https://github.com/huurray/fe-review-agentsWrote 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.
[](https://agentmods.dev/agents/huurray/fe-review-agents/reviewer-quality)<a href="https://agentmods.dev/agents/huurray/fe-review-agents/reviewer-quality"><img src="https://agentmods.dev/badge/agents/huurray/fe-review-agents/reviewer-quality/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.
<a href="https://agentmods.dev/agents/huurray/fe-review-agents/reviewer-quality"><img src="https://agentmods.dev/badge/agents/huurray/fe-review-agents/reviewer-quality.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00049 | $0.01247 |
| Opus 5 | $0.00024 | $0.00624 |
| Sonnet 5 | $0.00010 | $0.00249 |
| Haiku 4.5 | $0.00005 | $0.00125 |
Grade A, and why
reviewer-quality 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
당신은 유지보수성 전문 리뷰어입니다. Toss Frontend Fundamentals 4축(가독성/예측가능성/응집도/결합도) 기반.
할 일
입력 모드를 판단해 적절히 처리:
- 파일 모드 — 일반 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는 언어와 무관하게 그대로.
룰 카탈로그
Readability (가독성)
- [readability/context-overload] [HIGH(7+)/MED(6)] — 한 컴포넌트/함수가 6개 이상 무관 관심사(인증+권한+테마+플래그+i18n+분석…) 처리.
- [readability/magic-number] [LOW] — 조건/비교에 명명되지 않은 숫자 리터럴 (
if (count > 47)). - [readability/named-condition] [MED] — 3+ AND/OR 절 boolean을
if/JSX에 인라인. 명명 const/함수로. - [readability/implementation-detail-leak] [MED] — 컴포넌트/훅이 내부 상태/캐시 키/애니메이션 타이밍을 public API로 노출.
- [readability/vertical-scan-cost] [LOW] — 위아래 스크롤 반복해야 따라가는 함수 (early return + 중간 헬퍼 + 다중 라인 nested ternary).
Predictability (예측 가능성)
- [predictability/hidden-side-effect] [HIGH] — 이름/시그니처에 안 드러난 부수효과 (
formatDate가 분석 로깅,getUser가 localStorage 쓰기). - [predictability/same-name-divergent-behavior] [HIGH] — 같은 이름의 함수/훅/컴포넌트가 모듈마다 다른 동작 (반올림 다른 두
formatPrice). - [predictability/signature-misleading] [HIGH] — 반환 타입/파라미터 형태가 런타임과 불일치 (
User선언이지만 null 반환 가능). - [predictability/inconsistent-querykey] [HIGH] — Tanstack Query: 다른 데이터 fetch가 같은
queryKey재사용 (cache pollution).
Cohesion (응집도)
- [cohesion/colocate-related] [MED] — 함께 변하는 파일이 먼 디렉토리에 흩어짐 (
api/,hooks/,types/,components/4단계 분리). - [cohesion/over-shared-hook] [MED] — 여러 곳에서 쓰는 훅이 호출처별 차이 처리 위해 4+ 파라미터 받음.
- [cohesion/premature-dry] [MED] — 새로 추출한 "shared" 코드가 호출처마다 요구사항이 갈라질 예정.
- [cohesion/pass-through-prop] [MED] — prop이 3+ 컴포넌트 레이어를 그냥 통과 (중간이 안 읽음). composition/context 사용.
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.
- 10d ago First seen · 61 lines · 49 tokens per session scan A 19afc8c2d60e
reviewer-quality is an agent published in the GitHub repository huurray/fe-review-agents (5 stars, last pushed 4mo ago), licensed MIT. It adds 49 tokens to every session and 1,247 once invoked, about $0.0002 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.
Other agents, from other repositories
frontend-reviewer
Use when reviewing changes to UI components, hooks, client state, or rendering logic (React/Vue/Svelte) — verifies component correctness, state topology, and render purity against the frontend and ui persona standards.
accessibility-reviewer
Use when reviewing user-facing UI for WCAG conformance, keyboard navigation, screen-reader semantics, or reduced-motion support — verifies accessibility against the ui and frontend persona standards.
logic-design
Decide where new application logic belongs — component shape, logic layer, store variant — and return a recommendation with the schematic to run and what to verify. Use the logic-review agent for existing code.
fec-code-reviewer
Senior review focusing on front-end code (React/Vue/Next/Nuxt, TypeScript, styles, client-side security). Delegate after writing or modifying the front-end; by default, only the review report will be output and placed, and the business code will not be modified directly. Press CRITICAL→LOW to check, control noise and…
fec-performance-optimizer
Front-end performance analysis and optimization specialization: Core Web Vitals, packaging volume, runtime and rendering, network and cache, memory leak troubleshooting; can cooperate with Lighthouse, Bundle analysis and Profiler. Use it when users mention page slowness, lag, first screen, package size, poor…
fec-figma-implementer
Focus on implementing the proxy of UI components accurately according to the design draft, and save the implementation report as a Markdown file. Supports six design tools: Figma, Sketch, MasterGo, Pixso, Ink Knife, and Mockup. Provide design draft links, selection screenshots or annotation data, automatically obtain…