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 react-router-loader-boundarygit 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/react-router-loader-boundary)<a href="https://agentmods.dev/skills/s977043/river-review/react-router-loader-boundary"><img src="https://agentmods.dev/badge/skills/s977043/river-review/react-router-loader-boundary.svg" alt="Measured on agentmods" 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.00039 | $0.00982 |
| Opus 5 | $0.00019 | $0.00491 |
| Sonnet 5 | $0.00008 | $0.00196 |
| Haiku 4.5 | $0.00004 | $0.00098 |
Grade A, and why
React Router Loader Boundary Review 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 4d 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.
What it actually says
Pattern declaration
Primary pattern: Reviewer Secondary patterns: Inversion Why: React Router framework mode の data loading 規約への適合をチェックリスト型で検査する
Goal / 目的
- ルート遷移で確定するデータが
useEffect+ fetch でコンポーネント取得されること（二重フェッチ・レース・hydration mismatch の温床）を防ぐ。 - loader / clientLoader の境界違反（loader 内のクライアント専用 API、clientLoader 内のサーバー専用 API）を検出する。
Non-goals / 扱わないこと
- action / mutation の規約（
react-router-action-contractのスコープ）。 - data mode / declarative mode のコード（framework mode のルートモジュールのみ対象）。
- 一般的な React パフォーマンス（modern-web 系 skill のスコープ）。
Pre-execution Gate / 実行前ゲート
このスキルは以下の条件がすべて満たされない限りNO_REVIEWを返す。
- 差分が React Router framework mode のルートモジュール（loader / clientLoader / action の export、または routes 配下）に関係する
- diff コンテキストが利用可能である
ゲート不成立時の出力: NO_REVIEW: react-router-loader-boundary — framework mode ルートの変更なし
False-positive guards / 抑制条件
useEffect+ fetch が ナビゲーションに紐づかない データの場合は指摘しない（ポーリング、WebSocket、リアルタイム更新、サードパーティ SDK 初期化）。「URL / ルート遷移で確定するデータか」で判定する。- 親ルートの loader で取得済みデータを子が利用する設計は正当。
- data mode / declarative mode のコードには適用しない（モード誤判定が最大の誤検出源）。
Rule / ルール
- ルート遷移で確定する初期データは
loader（SSR、サーバー専用 API はクライアントバンドルから自動除去される）に置く。 - ブラウザ専用データは
clientLoaderに置き、hydrate する場合はHydrateFallbackを定義する（clientLoader.hydrate = true as constのas const欠落も指摘）。 loader内でクライアント専用 API（window / localStorage 等）、clientLoader内でサーバー専用 API（DB 直接アクセス等）を使っていないか確認する。- loader の返却値はシリアライズ可能型に限る（class instance の返却を指摘）。
Evidence / 根拠の取り方
- 指摘は
<file>:<line>で差分に紐づけ、該当する公式規約（reactrouter.com/start/framework/data-loading）を 1 行で添える。 - ナビゲーション紐づきの判断が割れる場合は断定せず
questionsで返す。
Output / 出力（短文版の推奨）
コメントは日本語で返す。
- Finding: どの境界規約に反しているか（1文）
- Impact: 二重フェッチ / hydration mismatch / バンドル漏えい等の影響
- Fix: loader / clientLoader への移動案（最小）
Sources / 出典
- React Router — Data Loading: https://reactrouter.com/start/framework/data-loading
What ships with it
3 files 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.
- 4d ago First seen · 73 lines · 39 tokens per session scan A cefcbbfbd4e6
React Router Loader Boundary Review is a skill published in the GitHub repository s977043/river-review (3 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 982 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-09-03.
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…
tailwind-css
Tailwind CSS v4 patterns: CSS-first config, utility classes, component variants, v3 migration. Use when styling with Tailwind, configuring @theme tokens, using tailwind-variants/CVA, migrating v3 to v4, or fixing Tailwind styles and dark mode.
testing-react
Writes React/TypeScript tests using Vitest and React Testing Library. Use when "write react tests", "vitest", "component test", "hook test", "RTL", "testing library", "snapshot test", or testing React components, hooks, and utilities.
react-effects-audit
Use when auditing React or Next.js components for unnecessary or unsafe useEffect usage -- detects 9 anti-patterns from "You Might Not Need an Effect".
fec-route-protection
A guide for protecting front-end routes, meaning the pages and URLs of a web application, based on whether someone is signed in and what permissions they have. It covers login checks, role-based access, expired sessions, and redirects.
fec-state-management
A guide for deciding where an application's changing information should live, such as inside a component, in the URL, in a form, in a browser cache, or in a shared store. A store is a shared place for client-side information used across parts of an app.