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 instructions/foxted/rsc-boundary/agents-mdgit 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/instructions/foxted/rsc-boundary/agents-md)<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="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 | $0.01189 | $0.01189 |
| Opus 5 | $0.00594 | $0.00594 |
| Sonnet 5 | $0.00238 | $0.00238 |
| Haiku 4.5 | $0.00119 | $0.00119 |
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 4d 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 — 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 rootpackageManager). - 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).
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.
- 4d ago First seen · 71 lines · 1,189 tokens per session scan A 1216c0740925
rsc-boundary AGENTS.md is an instructions file published in the GitHub repository foxted/rsc-boundary (126 stars, last pushed 1mo ago), licensed MIT. It adds 1,189 tokens to every session, about $0.0059 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 instructions, from other repositories
core CLAUDE.md
Claude Code instructions for module-federation/core, covering claude task parallelization & development guidelines, core principles, maximum parallelization strategy, universal parallel task patterns and for any codebase task.
data-table-filters CLAUDE.md
Claude Code instructions for openstatusHQ/data-table-filters, covering claude.md, project overview, monorepo structure (pnpm + turborepo), key commands and database.
coss AGENTS.md
AGENTS.md instructions for cosscom/coss, covering agents.md and main documentation.
vibedgames CLAUDE.md
Claude Code instructions for kyh/vibedgames, covering agent instructions, agent-driven development, what this is, product & business context and key architectural decisions.
storefront AGENTS.md
AGENTS.md instructions for saleor/storefront, covering saleor paper — agent guide (always-on), how to get context (read in this order; stop when answered), precedence, critical commands and non-negotiable rules.
pip-web CLAUDE.md
Claude Code instructions for playpip/pip-web, covering claude.md — agent guide for pip, read first (by task), the three layers (respect the boundaries), non-negotiables and commands / definition of done.