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.
npx skills add s977043/river-review --skill river-review-frontendgit clone --depth 1 https://github.com/s977043/river-reviewWrote 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/skills/s977043/river-review/river-review-frontend)<a href="https://agentmods.dev/skills/s977043/river-review/river-review-frontend"><img src="https://agentmods.dev/badge/skills/s977043/river-review/river-review-frontend/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/skills/s977043/river-review/river-review-frontend"><img src="https://agentmods.dev/badge/skills/s977043/river-review/river-review-frontend.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.00072 | $0.02988 |
| Opus 5 | $0.00036 | $0.01494 |
| Sonnet 5 | $0.00014 | $0.00598 |
| Haiku 4.5 | $0.00007 | $0.00299 |
Grade A, and why
river-review-frontend 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 11d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Review（フロントエンドレビュー）
UI/コンポーネント変更に影響するアクセシビリティ、デザインシステム準拠、フレームワーク境界を検出し、適切な個別スキルで検証する。
frontend-reviewer（review-team perspective ロール）とは別物:src/lib/reviewer-orchestrator.mjsのfrontend-reviewerは review-team のマルチエージェントレビューで Claude/Codex が演じる perspective ロール（UI/component/styling ファイル検知時に自動追加）。本スキルは agent-skills ルーター群の一員で、キーワードから個別 registry skill へルーティングする別サーフェス。2つは独立して動作し、互いを呼び出さない。
When to Use / いつ使うか
- UI コンポーネント・スタイリングの変更時
- アクセシビリティ（a11y）に関わる変更時
- デザインシステム・デザイントークンの準拠確認が必要なとき
- Tailwind クラスの衛生確認が必要なとき
- Next.js App Router / React Router のフレームワーク境界チェックが必要なとき
- 他の専門エージェント（architecture, security, performance, testing, code）に該当しない UI 固有の懸念があるとき
Routing / ルーティング
| キーワード | スキルID | 説明 |
|---|---|---|
| a11y, アクセシビリティ, alt属性, aria-label | a11y-accessible-name |
アクセシビリティ基本 |
| キーボード操作, フォーカス管理, ARIA role | modern-web-a11y-interactive |
インタラクティブ UI アクセシビリティ |
| セマンティック, div クリック, ネイティブ要素 | modern-web-semantic |
セマンティック HTML・プラットフォームネイティブ |
| ブラウザ互換, Baseline, feature detection | modern-web-browser-compat |
ブラウザ互換性・Baseline |
| デザインシステム, コンポーネント再利用, Button | design-system-component-reuse |
デザインシステム コンポーネント再利用 |
| デザイントークン, 色の直書き, 余白, 角丸 | design-token-enforcement |
デザイントークン |
| DESIGN.md, デザイン定義準拠, スケール逸脱 | design-source-conformance |
デザイン Source-of-Truth 準拠 |
| Tailwind, 任意値, クラス衛生 | tailwind-class-hygiene |
Tailwind クラス衛生 |
| ローディング, 空状態, スピナー, 状態欠落 | loading-state |
ローディング状態遷移 |
| コンポーネントバリアント, hover, focus, disabled | component-variants-states |
コンポーネント状態の文書化 |
| Next.js, App Router, use client | nextjs-app-router-boundary |
Next.js App Router 境界 |
| React Router, loader, useEffect データ取得 | react-router-loader-boundary |
React Router loader 境界 |
| React Router, action, ErrorBoundary | react-router-action-contract |
React Router action 契約 |
| Core Web Vitals, LCP, INP, CLS | modern-web-performance |
参照のみ。実行は river-review-performance（理由） |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 166 lines · 72 tokens per session scan A aba74d839c82
river-review-frontend is a skill published in the GitHub repository s977043/river-review (3 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 2,988 once invoked, about $0.0004 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 skills, from other repositories
component-api-validator
Audit component APIs for consistency, breaking changes, TypeScript coverage, and contract compliance across a component library. Trigger when someone says: component prop review, verify component types are exported, component API audit, check our component interfaces, are our props consistent, API consistency check…
design-with-claude
Use when design work needs a product designer's eye: auditing a codebase for design-system gaps, fixing WCAG contrast and unlabeled inputs, choosing type scales or spacing steps, reviewing UI that looks generic or AI-generated, or designing forms, tables, dashboards, navigation, checkout, onboarding, dark mode, and…
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", or "vs best practices".
a11y-audit
Accessibility audit covering WCAG 2.2, contrast, focus, keyboard, screen reader, and touch targets. Use when the user asks for an accessibility audit, an a11y review, a WCAG check, an accessibility check, or an a11y audit.
color-audit
Color-only audit that extracts, evaluates, and recommends improvements for the project's color system. Use when the user asks to audit colors, run a color review or color audit, fix their colors, or work on the color palette or color system.
theme-builder
Build a light/dark theme from scratch or improve an existing one, with a complete surface, text, and interactive color system. Use when the user asks to build or create a theme, use the theme builder, or set up a light and dark theme.