SurfSense is an open-source desktop application that uses an AI agent to research, transform, and edit documents while keeping their index on the user's machine. It is intended for people working with documents they cannot upload, with a choice of local or remote models and no account required.
Borrowing it
Nothing to install: this file belongs to MODSetter/SurfSense. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/MODSetter/SurfSense/main/.agents/skills/frontend-workflow/react-performance/SKILL.mdgit clone --depth 1 https://github.com/MODSetter/SurfSenseWrote 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/modsetter/surfsense/react-performance)<a href="https://agentmods.dev/skills/modsetter/surfsense/react-performance"><img src="https://agentmods.dev/badge/skills/modsetter/surfsense/react-performance/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/modsetter/surfsense/react-performance"><img src="https://agentmods.dev/badge/skills/modsetter/surfsense/react-performance.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.00000 | $0.01787 |
| Opus 5.5 | $0.00000 | $0.00715 |
| Sonnet 5.5 | $0.00000 | $0.00357 |
| Haiku 4.5 | $0.00000 | $0.00179 |
Grade A, and why
react-performance 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 28d 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- vercel-react-best-practices — 98% identical, 5 lines differ
- vercel-react-best-practices — 97% identical, 3 lines differ
- vercel-react-best-practices — 97% identical, 3 lines differ
- vercel-react-best-practices — 97% identical, 3 lines differ
- vercel-react-best-practices — 97% identical, 3 lines differ
- vercel-react-best-practices — 97% identical, 25 lines differ
- vercel-react-best-practices — 97% identical, 25 lines differ
- vercel-react-best-practices — 97% identical, 3 lines differ
How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: vercel-react-best-practices description: React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements. license: MIT metadata: author: vercel version: "1.0.0"
Vercel React Best Practices
Comprehensive performance optimization guide for React and Next.js applications, maintained by Vercel. Contains 70 rules across 8 categories, prioritized by impact to guide automated refactoring and code generation.
When to Apply
Reference these guidelines when:
- Writing new React components or Next.js pages
- Implementing data fetching (client or server-side)
- Reviewing code for performance issues
- Refactoring existing React/Next.js code
- Optimizing bundle size or load times
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Eliminating Waterfalls | CRITICAL | async- |
| 2 | Bundle Size Optimization | CRITICAL | bundle- |
| 3 | Server-Side Performance | HIGH | server- |
| 4 | Client-Side Data Fetching | MEDIUM-HIGH | client- |
| 5 | Re-render Optimization | MEDIUM | rerender- |
| 6 | Rendering Performance | MEDIUM | rendering- |
| 7 | JavaScript Performance | LOW-MEDIUM | js- |
| 8 | Advanced Patterns | LOW | advanced- |
Quick Reference
1. Eliminating Waterfalls (CRITICAL)
async-cheap-condition-before-await- Check cheap sync conditions before awaiting flags or remote valuesasync-defer-await- Move await into branches where actually usedasync-parallel- Use Promise.all() for independent operationsasync-dependencies- Use better-all for partial dependenciesasync-api-routes- Start promises early, await late in API routesasync-suspense-boundaries- Use Suspense to stream content
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.
- rules-compiled.md 106 KB
- rules/_sections.md 1.5 KB
- rules/_template.md 631 B
- rules/advanced-effect-event-deps.md 1.8 KB
- rules/advanced-event-handler-refs.md 1.4 KB
- rules/advanced-init-once.md 958 B
- rules/advanced-use-latest.md 1.0 KB
- rules/async-api-routes.md 1.1 KB
- rules/async-cheap-condition-before-await.md 1.2 KB
- rules/async-defer-await.md 2.2 KB
- rules/async-dependencies.md 1.3 KB
- rules/async-parallel.md 654 B
- rules/async-suspense-boundaries.md 2.5 KB
- rules/bundle-analyzable-paths.md 2.3 KB
- rules/bundle-barrel-imports.md 2.7 KB
- rules/bundle-conditional.md 949 B
- rules/bundle-defer-third-party.md 920 B
- rules/bundle-dynamic-imports.md 791 B
- rules/bundle-preload.md 1.1 KB
- rules/client-event-listeners.md 1.9 KB
- rules/client-localstorage-schema.md 1.9 KB
- rules/client-passive-event-listeners.md 1.6 KB
- rules/client-swr-dedup.md 1.1 KB
- rules/js-batch-dom-css.md 3.2 KB
- rules/js-cache-function-results.md 1.9 KB
- rules/js-cache-property-access.md 532 B
- rules/js-cache-storage.md 1.6 KB
- rules/js-combine-iterations.md 753 B
- rules/js-early-exit.md 1.1 KB
- rules/js-flatmap-filter.md 1.4 KB
- rules/js-hoist-regexp.md 1.0 KB
- rules/js-index-maps.md 837 B
- rules/js-length-check-first.md 1.7 KB
- rules/js-min-max-loop.md 2.2 KB
- rules/js-request-idle-callback.md 2.6 KB
- rules/js-set-map-lookups.md 532 B
- rules/js-tosorted-immutable.md 1.7 KB
- rules/rendering-activity.md 564 B
- rules/rendering-animate-svg-wrapper.md 1.2 KB
- rules/rendering-conditional-render.md 980 B
- rules/rendering-content-visibility.md 815 B
- rules/rendering-hoist-jsx.md 1.0 KB
- rules/rendering-hydration-no-flicker.md 2.3 KB
- rules/rendering-hydration-suppress-warning.md 872 B
- rules/rendering-resource-hints.md 2.5 KB
- rules/rendering-script-defer-async.md 1.8 KB
- rules/rendering-svg-precision.md 588 B
- rules/rendering-usetransition-loading.md 2.0 KB
- rules/rerender-defer-reads.md 973 B
- rules/rerender-dependencies.md 824 B
- rules/rerender-derived-state-no-effect.md 1.2 KB
- rules/rerender-derived-state.md 728 B
- rules/rerender-functional-setstate.md 2.9 KB
- rules/rerender-lazy-state-init.md 2.0 KB
- rules/rerender-memo-with-default-value.md 1.1 KB
- rules/rerender-memo.md 1.1 KB
- rules/rerender-move-effect-to-event.md 1.2 KB
- rules/rerender-no-inline-components.md 2.1 KB
- rules/rerender-simple-expression-in-memo.md 1018 B
- rules/rerender-split-combined-hooks.md 1.8 KB
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.
- 28d ago First seen · 151 lines · 0 tokens per session scan A 15942111befe
react-performance is a skill published in the GitHub repository MODSetter/SurfSense (16,464 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,787 tokens. 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-19.
Other skills, from other repositories
langchain
Framework for building LLM-powered applications with agents, chains, and RAG. Supports multiple providers (OpenAI, Anthropic, Google), 500+ integrations, ReAct agents, tool calling, memory management, and vector store retrieval. Use for building chatbots, question-answering systems, autonomous agents, or RAG…
first-reader
Beta readers for any draft, run by simulating how a real reader experiences it, moment by moment. A skim gate, a no-lookahead timed read producing an attention transcript with quit points, a recall test of what a reader remembers the next day, and a trust ledger of the implied author. Use when the user asks for a beta…
mcp-apps-builder
MANDATORY for ALL MCP server work - mcp-use framework best practices and patterns. READ THIS FIRST before any MCP server work, including: Creating new MCP servers Modifying existing MCP servers (adding/updating tools, resources, prompts, widgets) Debugging MCP server issues or errors Reviewing MCP server code for…
project-graveyard
Scans the developer's machine for dead side projects, autopsies each one from its git history (died at the payments wall, killed by a newer project, finished but never shipped), surfaces their personal death patterns, and picks the corpse most worth resurrecting — then helps ship it. Use when the user mentions…
commit-archaeologist
Reconstructs why code exists from local git history, including the introducing commit, later changes, current authors, repeated companion files, and likely intent. Use when the user asks "why does this code exist", "who wrote this function and why", or to "explain the history of this function" before a rewrite…
dependency-doctor
Checks requirements.txt, pyproject.toml, and package.json dependency manifests for surface-level direct-dependency footguns: standard-library shadowing pins, abandoned backports, unpinned dependencies, and obvious intra-manifest conflicts, plus opt-in PyPI yanked releases. Use when the user asks to check a manifest…