What is rsc-boundary AGENTS.md?

Repository instructions for rsc-boundary, a tool that shows which parts of a React application run on the server and which run in the browser. They describe the monorepo, a codebase containing several related packages and apps, and its commands.

Use them when working on rsc-boundary, especially when changing its core package, Next.js or TanStack Start adapters, demo site, or test playgrounds.

They give contributors a shared map of the project, helping keep changes in the correct package or app and consistent with the existing layout.

How foxted/rsc-boundary configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to foxted/rsc-boundary. 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/foxted/rsc-boundary/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/foxted/rsc-boundary

Made for: Codex, OpenCode.

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/foxted/rsc-boundary/agents-md/github.svg)](https://agentmods.dev/instructions/foxted/rsc-boundary/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/foxted/rsc-boundary/agents-md"><img src="https://agentmods.dev/badge/instructions/foxted/rsc-boundary/agents-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/foxted/rsc-boundary/agents-md"><img src="https://agentmods.dev/badge/instructions/foxted/rsc-boundary/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,189 This file is loaded in full into every session.

When invoked 1,189 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.01189	$0.01189
Opus 5.5	$0.00476	$0.00476
Sonnet 5.5	$0.00238	$0.00238
Haiku 4.5	$0.00119	$0.00119

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

Security

Grade A, and why

rsc-boundary AGENTS.md 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 2mo 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.md · 71 lines

How it starts

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

AGENTS.md — RSC Boundary

Guidance for AI and human contributors. Keep changes scoped and consistent with this layout.

Purpose

Monorepo for RSC Boundary: tooling that visualizes the boundary between React Server Components and Client Components in any RSC-capable React framework. Published packages live under packages/; the demo site lives under apps/web; lightweight adapter smoke-tests live under playgrounds/.

Layout

Path	Role
`packages/core`	`@rsc-boundary/core` — framework-agnostic: fiber walk, highlights, devtools UI, `FrameworkAdapter` contract.
`packages/next`	`@rsc-boundary/next` — Next.js App Router adapter + `RscBoundaryProvider`.
`packages/start`	`@rsc-boundary/start` — TanStack Start adapter + `RscBoundaryProvider`.
`apps/web`	Next.js app: marketing, docs snippets, interactive examples. Depends on `@rsc-boundary/next` via `workspace:*`.
`playgrounds/next`	Minimal Next.js 16 App Router app that smoke-tests `@rsc-boundary/next`. Private, not published.
`playgrounds/start`	Minimal TanStack Start app that smoke-tests `@rsc-boundary/start`. Private, not published.
`config/eslint-config`, `config/typescript-config`	Shared ESLint and TypeScript configs (`@repo/eslint-config`, `@repo/typescript-config`).

Rule of thumb:

Framework-agnostic detection / highlight logic → packages/core.
Next.js-specific adapter changes (internals list, root element) → packages/next.
TanStack Start-specific adapter changes → packages/start.
Wiring, copy, and example routes for the public site → apps/web.

Stack

Package manager: pnpm (see root packageManager).
Monorepo: Turborepo (turbo.json).
App: Next.js App Router, React 19, TypeScript strict.

Commands (repo root)

pnpm install
pnpm dev          # turbo run dev
pnpm build        # turbo run build
pnpm lint         # turbo run lint
pnpm check-types  # turbo run check-types

Run a single workspace with pnpm --filter <name> <script> (e.g. pnpm --filter web dev).

Read the full file on GitHub · 71 lines

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.

2mo ago First seen · 71 lines · 1,189 tokens per session scan A 1216c0740925

Subscribe to this mod's changes

rsc-boundary AGENTS.md is an instructions file published in the GitHub repository foxted/rsc-boundary (129 stars, last pushed 2mo ago), licensed MIT. It adds 1,189 tokens to every session, about $0.0048 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.

Frontend React devtools nextjs react-server-components rsc

rsc-boundary AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
rsc-boundary AGENTS.mdfoxted/rsc-boundary	Instructions file	129	2mo ago	MIT	A	1,189	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

rsc-boundary: Instructions file for Codex