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 agentmods add skills/foxted/rsc-boundary/install-nextnpx skills add foxted/rsc-boundary --skill install-nextgit clone --depth 1 https://github.com/foxted/rsc-boundaryWrote 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/foxted/rsc-boundary/install-next)<a href="https://agentmods.dev/skills/foxted/rsc-boundary/install-next"><img src="https://agentmods.dev/badge/skills/foxted/rsc-boundary/install-next.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.00082 | $0.01046 |
| Opus 5 | $0.00041 | $0.00523 |
| Sonnet 5 | $0.00016 | $0.00209 |
| Haiku 4.5 | $0.00008 | $0.00105 |
Grade A, and why
install-next 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 6d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Install RSC Boundary in a Next.js app
Package: @rsc-boundary/next on npm. The unscoped rsc-boundary package on npm is deprecated — for new projects always install @rsc-boundary/next (it pulls in @rsc-boundary/core automatically).
Prerequisites
- Next.js 16+ with the App Router
- React 19+ and react-dom 19+ (peer dependencies)
If versions are older, say so and recommend upgrading before installing.
1. Install the dependency
Use the project's package manager:
pnpm add @rsc-boundary/next
npm install @rsc-boundary/next
yarn add @rsc-boundary/next
Migrating from rsc-boundary
If the user still has the deprecated unscoped rsc-boundary package installed, the migration is a one-liner:
pnpm remove rsc-boundary && pnpm add @rsc-boundary/next
Then replace the import everywhere (one global find-and-replace):
-import { ... } from "rsc-boundary";
+import { ... } from "@rsc-boundary/next";
The API surface is identical — no other code changes are needed.
Monorepo / local development
If the user is working inside this repository and consuming the package from the workspace, use the workspace protocol:
"@rsc-boundary/next": "workspace:*"
Ensure the packages are built (pnpm --filter @rsc-boundary/next build, which also builds core) before the app typechecks against dist/.
2. Wrap the App Router root layout
Edit app/layout.tsx (or the file that exports the root RootLayout for app/).
-
Import the provider:
import { RscBoundaryProvider } from "@rsc-boundary/next"; -
Wrap
{children}(inside<body>) with<RscBoundaryProvider>{children}</RscBoundaryProvider>.
Preserve existing structure: fonts, metadata, other layout UI, and className on <body> / <html> stay as they are—only add the provider around the main content tree as appropriate.
Minimal pattern:
import { RscBoundaryProvider } from "@rsc-boundary/next";
export default function RootLayout({
children,
}: {
children: React.ReactNode;
}) {
return (
<html lang="en">
<body>
<RscBoundaryProvider>{children}</RscBoundaryProvider>
</body>
</html>
);
}
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.
- 6d ago First seen · 126 lines · 82 tokens per session scan A 23b7aa2c1bf8
install-next is a skill published in the GitHub repository foxted/rsc-boundary (126 stars, last pushed today), licensed MIT. It adds 82 tokens to every session and 1,046 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
zustand-docs
Zustand — small, fast, scalable state management for React. Store creation, hooks, middleware, TypeScript.
nextjs
Next.js App Router best practices — Server Components, data fetching, caching, routing, middleware, metadata, error handling, streaming, Server Actions, and performance optimization for Next.js 14-16+.
tanstack-start-rsc
Implement, review, debug, and refactor TanStack Start React Server Components in React 19 apps. Use when tasks mention @tanstack/react-start/rsc, renderServerComponent, createCompositeComponent, CompositeComponent, renderToReadableStream, createFromReadableStream, createFromFetch, Composite Components, React Flight…
migrate-radix-to-base
Migrates React projects and components from Radix UI to Base UI. Use when asked to migrate from radix, move to base-ui, convert radix primitives, or switch a shadcn project's base library. Handles single components ("migrate accordion") and whole projects.
reskin
Author a NEW skin for the reskinnable-demo app. A skin is a self-contained domain plugin under src/skins/ / that implements the frozen Skin contract (src/shell/skin-contract.ts) to swap the app's entire experience — brand, theme, layout, pages, tools, data, and agent — as a live sales demo. Use when the user says "add…
copilotkit-channels
Use for the CODE half of a managed Intelligence Channel with Slack or Microsoft Teams: customising the Channel a CLI-scaffolded project already ships, or — for a project the CLI did not generate — writing the Channel declaration, the long-running host, and the awaited activation call. Teams provider setup is in scope…