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 Heyvhuang/ship-faster --skill review-react-best-practicesgit clone --depth 1 https://github.com/Heyvhuang/ship-fasterWrote 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/heyvhuang/ship-faster/review-react-best-practices)<a href="https://agentmods.dev/skills/heyvhuang/ship-faster/review-react-best-practices"><img src="https://agentmods.dev/badge/skills/heyvhuang/ship-faster/review-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.
<a href="https://agentmods.dev/skills/heyvhuang/ship-faster/review-react-best-practices"><img src="https://agentmods.dev/badge/skills/heyvhuang/ship-faster/review-react-best-practices.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00073 | $0.00641 |
| Opus 5 | $0.00036 | $0.00320 |
| Sonnet 5 | $0.00015 | $0.00128 |
| Haiku 4.5 | $0.00007 | $0.00064 |
Grade A, and why
review-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 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React Best Practices Review (Performance-First)
Use this skill to turn “React feels slow / Next.js page is heavy / too many requests” into a repeatable, prioritized review.
This skill is intentionally built like a rule library:
SKILL.md: how to review + how to search rulesreferences/rules/*: one rule per file (taggable, sortable, easy to evolve)
When to apply
Use when:
- Building or refactoring React components
- Working in Next.js (App Router) on RSC boundaries, Server Actions, data fetching
- Reviewing PRs for performance regressions
- Bundle size increases / slow HMR / cold start issues
- UI jank / unnecessary re-renders / hydration issues
Review method (prioritized)
- Start with CRITICAL rules first (waterfalls + bundle).
- Only then go to HIGH (server patterns + serialization).
- Then MEDIUM (re-render + rendering).
- Then LOW-MEDIUM micro-optimizations (JS hot paths).
Section ordering lives in: references/rules/_sections.md
How to use the rules efficiently
Search by keyword
rg -n "waterfall|Promise\\.all|defer await" references/rules
rg -n "barrel|optimizePackageImports|dynamic" references/rules
rg -n "cache\\(|React\\.cache|serialization|RSC" references/rules
rg -n "memo\\(|useMemo|useCallback|dependencies" references/rules
Search by tag
Each rule has tags: in YAML frontmatter.
rg -n "tags:.*bundle" references/rules
rg -n "tags:.*rerender" references/rules
Output format (recommended)
When reviewing code, output:
- Summary (1 paragraph)
- Critical fixes (must-fix, biggest wins)
- High impact (should-fix)
- Medium / Low (nice-to-have)
For each issue include:
- Rule name (and file under
references/rules/) - Location (
path:line) - Why it matters (latency / bundle / CPU / UX)
- Minimal fix direction (prefer small diffs)
If running in a Ship Faster run directory, persist the report to:
run_dir/evidence/react-best-practices-review.md
What ships with it
25 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.
- references/rules/_sections.md 1.4 KB
- references/rules/_template.md 468 B
- references/rules/advanced-event-handler-refs.md 795 B
- references/rules/async-api-routes-no-waterfall.md 1.0 KB
- references/rules/async-defer-await.md 919 B
- references/rules/async-parallel-promises.md 870 B
- references/rules/async-promise-all.md 586 B
- references/rules/async-suspense-streaming.md 990 B
- references/rules/bundle-avoid-barrel-imports.md 977 B
- references/rules/bundle-defer-third-party.md 657 B
- references/rules/bundle-dynamic-imports.md 757 B
- references/rules/bundle-preload-intent.md 630 B
- references/rules/client-dedupe-event-listeners.md 729 B
- references/rules/client-dedupe-fetching.md 763 B
- references/rules/js-batch-dom-css.md 526 B
- references/rules/js-use-set-map-lookups.md 544 B
- references/rules/rendering-conditional-render.md 582 B
- references/rules/rendering-content-visibility.md 498 B
- references/rules/rendering-hoist-static-jsx.md 645 B
- references/rules/rerender-extract-memoized.md 1019 B
- references/rules/rerender-lazy-state-init.md 565 B
- references/rules/rerender-narrow-deps.md 709 B
- references/rules/server-cache-cross-request.md 874 B
- references/rules/server-minimize-serialization.md 773 B
- references/rules/server-react-cache-dedupe.md 783 B
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 · 80 lines · 73 tokens per session scan A 64c2ddc68e95
review-react-best-practices is a skill published in the GitHub repository Heyvhuang/ship-faster (339 stars, last pushed 26d ago), licensed MIT. It adds 73 tokens to every session and 641 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-30.
Other skills, from other repositories
compiler-commit
Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix.
compiler-verify
Use when you need to run all compiler checks (tests, lint, format) before committing. Detects whether TS or Rust code changed and runs the appropriate checks.
compiler-review
Review Rust port code for port fidelity, convention compliance, and error handling. Compares against the original TypeScript source.
ss-lint
Quick automated lint — detects common design system violations in seconds.
recipe-front-review
Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.
frontend-code-review
Trigger when the user requests a review of frontend files (e.g., .tsx, .ts, .js). Support both pending-change reviews and focused file reviews while applying the checklist rules.