React Starter Kit is a full-stack monorepo template for building SaaS web applications with React, TypeScript, tRPC, and Cloudflare Workers. A monorepo keeps related applications and packages in one repository, while the template provides frontend, backend, authentication, billing, database, and development-tool foundations. The catalogue instructions, skills, and command help developers work with this starter kit.
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 kriasoft/react-starter-kit --skill merge-seedgit clone --depth 1 https://github.com/kriasoft/react-starter-kitWrote 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/kriasoft/react-starter-kit/merge-seed)<a href="https://agentmods.dev/skills/kriasoft/react-starter-kit/merge-seed"><img src="https://agentmods.dev/badge/skills/kriasoft/react-starter-kit/merge-seed/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/kriasoft/react-starter-kit/merge-seed"><img src="https://agentmods.dev/badge/skills/kriasoft/react-starter-kit/merge-seed.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk warn
- 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.00049 | $0.01489 |
| Opus 5.5 | $0.00020 | $0.00596 |
| Sonnet 5.5 | $0.00010 | $0.00298 |
| Haiku 4.5 | $0.00005 | $0.00149 |
Grade A, and why
merge-seed 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Merge seed updates
This project is a fork of React Starter Kit. seed/main is upstream; main is upstream plus this project's divergence. Syncing is a recurring operation.
Core rule
Upstream owns mechanism. This project owns identity and scope.
Adopt from upstream: dependency and toolchain versions, build and config structure, framework API updates, refactors, newly required bindings and variables.
Keep local: names, domains, routes, worker and service identifiers; product copy and positioning; plans, features, scope; project-only integrations and config; deliberate additions and deletions.
When a hunk mixes both, take upstream's structure and reapply local values. Never take a whole side merely to clear a conflict — whole-file resolution is valid only where a rule below makes that side authoritative. The repository defines what counts as local identity and scope: AGENTS.md, docs/adr/, docs/product/, and the current config on main.
Merge
git status --short # must be clean
git remote get-url seed || git remote add seed https://github.com/kriasoft/react-starter-kit.git
git fetch seed
MB=$(git merge-base main seed/main)
git log --oneline "$MB..seed/main" # read before resolving anything
git switch -c "chore/merge-seed-$(git rev-parse --short seed/main)" main
git -c merge.conflictStyle=zdiff3 merge --no-ff --no-commit --no-rerere-autoupdate seed/main
git diff --name-only --diff-filter=U # unresolved conflicts
--no-commit stops git auto-committing a clean merge, so the commit and its subject are always ours to write. --no-rerere-autoupdate keeps every conflict in that list even when rerere has a recorded resolution to replay. If the branch already exists, an earlier sync was left unfinished — inspect it and resume or delete it deliberately, never force-reset over it.
rerere writes its replayed resolution straight into the working tree, so a conflicted file can arrive already looking finished. Treat pre-filled content as unreviewed; git rerere forget <path> to redo it.
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.
- 1mo ago First seen · 95 lines · 49 tokens per session scan A 86ab7204a2a8
merge-seed is a skill published in the GitHub repository kriasoft/react-starter-kit (23,696 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 1,489 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.
Other skills, from other repositories
next-upgrade
Upgrade Next.js to the latest version following official migration guides and codemods.
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
vercel-react-best-practices
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…
vercel-react-view-transitions
Guide for implementing smooth, native-feeling animations using React's View Transition API ( component, addTransitionType, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components…
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
draft-release-notes
Author the committed release-notes file for a Prisma 8 release (stable or 8.0.0-rc.N) by enumerating the merged PRs since the previous release v tag (stable or -rc.N), resolving opaque TML-NNNN: titles via Linear context (never copied verbatim), triaging public-worthiness, and writing categorized notes — breaking…