token_proxy: Skill for Codex

.agents/skills/react-best-practices/SKILL.md

react-best-practices is a skill for Codex from mxyhi/token_proxy. It costs 54 tokens per session (777 once invoked), scanned A, original, Apache-2.0.

A set of performance guidelines for React and Next.js applications, based on Vercel Engineering practices. React is a JavaScript library for user interfaces, while Next.js is a framework built around React.

In plain words
What is it for?
Use it when writing, reviewing, or refactoring React components, hooks, data fetching, rendering, bundles, asynchronous flows, or Next.js pages and server code.
Why use it?
It helps find slow rendering, unnecessary browser code, inefficient imports, and avoidable delays in data loading. The rules are selected according to the part of the application being changed.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents).

This is mxyhi/token_proxy's own configuration. It tells Codex how to work on token_proxy itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything token_proxy configures →

Reuse

Borrowing it

Nothing to install: this file belongs to mxyhi/token_proxy. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/mxyhi/token_proxy/main/.agents/skills/react-best-practices/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/mxyhi/token_proxy

Made for: Codex.

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.

agentmods badge for react-best-practices

README.md
[![agentmods](https://agentmods.dev/badge/skills/mxyhi/token_proxy/react-best-practices/github.svg)](https://agentmods.dev/skills/mxyhi/token_proxy/react-best-practices)
Your own site
<a href="https://agentmods.dev/skills/mxyhi/token_proxy/react-best-practices"><img src="https://agentmods.dev/badge/skills/mxyhi/token_proxy/react-best-practices/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.

agentmods 80×15 button for react-best-practices

Your own site · 80×15
<a href="https://agentmods.dev/skills/mxyhi/token_proxy/react-best-practices"><img src="https://agentmods.dev/badge/skills/mxyhi/token_proxy/react-best-practices.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 777 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00054 $0.00777
Opus 5.5 $0.00022 $0.00311
Sonnet 5.5 $0.00011 $0.00155
Haiku 4.5 $0.00005 $0.00078

Measured 1mo ago against content hash 6e30e0bbde47, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

react-best-practices 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 1mo 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/skills/react-best-practices/SKILL.md · 60 lines

How it starts

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

React Best Practices

Use this skill to apply Vercel Engineering's React and Next.js performance rules without loading the full 70-rule guide up front.

For this repository, treat React 19 + Vite + Tauri as the default app context. Next.js, RSC, and server-action rules apply only when editing Next.js code or reference projects.

Workflow

  1. Classify the task by performance surface.
  2. Read only the matching rule files under references/rules.
  3. Apply the smallest code change that matches the rule and the local code style.
  4. Verify with the nearest test, typecheck, build, or browser check.

Do not apply rules mechanically. Prefer evidence from the current component, data flow, and user interaction path.

Rule Groups

Read references/rules/_sections.md when you need the category index.

Priority Group Read When
1 async-* Removing async waterfalls, parallelizing independent work, delaying awaits until needed
2 bundle-* Reducing client bundle cost, dynamic imports, direct imports, third-party loading
3 server-* Next.js server code, RSC serialization, server caching, server fetch parallelism
4 client-* Client data fetching, SWR-style dedupe, browser storage, global event listeners
5 rerender-* Hooks, props, memoization, derived state, callback stability, frequent updates
6 rendering-* DOM/rendering cost, hydration behavior, content visibility, script/resource hints
7 js-* Hot JavaScript paths, repeated lookups, loops, storage reads, layout thrashing
8 advanced-* Effect events, latest refs, app initialization, stable callback refs

High-Signal Defaults

  • Start with async-* and bundle-* when performance problems are broad or user-visible.
  • For React component changes, check rerender-derived-state-no-effect.md, rerender-move-effect-to-event.md, and rerender-no-inline-components.md early.
  • Use event handlers for user actions. Use useEffect only to synchronize with external systems.
  • Avoid adding useMemo or memo for cheap primitive calculations. Read rerender-simple-expression-in-memo.md first.
  • For lists and repeated lookups, check js-index-maps.md, js-set-map-lookups.md, and rendering-content-visibility.md.
  • For this Tauri/Vite app, skip Next.js-only fixes unless the edited file is in a Next.js reference or the user asks for Next.js guidance.

Read the full file on GitHub · 60 lines

Files

What ships with it

60 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.

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. 1mo ago First seen · 60 lines · 54 tokens per session scan A 6e30e0bbde47

Subscribe to this mod's changes

react-best-practices is a skill published in the GitHub repository mxyhi/token_proxy (94 stars, last pushed yesterday), licensed Apache-2.0. It adds 54 tokens to every session and 777 once invoked, about $0.0002 per session on Opus 5.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-30.