Rsdoctor is a build analyzer for Rspack projects that shows how compilation works, what it produces, and where build problems occur. Development teams use it to inspect build artifacts and timing, check build rules, and add custom scans. The catalogue add-ons provide ways to work with Rsdoctor.
Borrowing it
Nothing to install: this file belongs to web-infra-dev/rsdoctor. 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/web-infra-dev/rsdoctor/main/AGENTS.mdgit clone --depth 1 https://github.com/web-infra-dev/rsdoctorWrote 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/web-infra-dev/rsdoctor/agents-md)<a href="https://agentmods.dev/instructions/web-infra-dev/rsdoctor/agents-md"><img src="https://agentmods.dev/badge/instructions/web-infra-dev/rsdoctor/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.
<a href="https://agentmods.dev/instructions/web-infra-dev/rsdoctor/agents-md"><img src="https://agentmods.dev/badge/instructions/web-infra-dev/rsdoctor/agents-md.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.01105 | $0.01105 |
| Opus 5.5 | $0.00442 | $0.00442 |
| Sonnet 5.5 | $0.00221 | $0.00221 |
| Haiku 4.5 | $0.00111 | $0.00111 |
Grade A, and why
rsdoctor 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 20d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Stack
- Node.js
22.18+, package manager pnpm12.6.0+(enable viacorepack enable) pnpmworkspace monorepo (topological build ordering)- TypeScript strict mode
- Lint/format: Rstack CLI (
rs lintbacked by Rslint,rs fmtbased on Prettier) - Test runner: Rstack CLI / Rstest (
pnpm test), E2E: Playwright (pnpm e2e)
Commands
# ── bootstrap ────────────────────────────────────────────────
pnpm install # install all deps + build all packages (prepare hook)
# ── quality checks ───────────────────────────────────────────
pnpm lint # rs lint (error-level only)
pnpm format # rs fmt
pnpm test # package tests via rs test (single worker, NODE_OPTIONS=--max-old-space-size=8192)
pnpm e2e # playwright e2e (requires chromium: cd e2e && npx playwright install chromium)
# ── build ────────────────────────────────────────────────────
pnpm run build # build all package targets in topological order
pnpm --filter '@rsdoctor/core...' run build # build one package and its workspace dependencies
# ── focused dev ──────────────────────────────────────────────
pnpm --filter @rsdoctor/core run build # build one package
pnpm --filter @rsdoctor/core run test # test one package
pnpm -C packages/client build # alternative: use directory path
Project structure
packages/
shared/ # shared types, utilities, and module / chunk / package graphs
core/ # Rspack plugin, analysis engine, rules, and server SDK
cli/ # `rsdoctor` CLI binary
agent-cli/ # `rsdoctor-agent` CLI for agent-facing report queries
client/ # web client (Rsbuild SPA, serves analysis report and report UI)
document/ # documentation site (Rspress)
scripts/
config/ # shared Rslib, Rstest, and TypeScript configuration
test-helper/ # test utilities shared across packages
e2e/ # Rstest + Playwright E2E tests
examples/ # runnable Rspack / Rsbuild / Rspress projects
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.
- 20d ago Changed · -14 lines · -135 tokens per session c8e8935d7cb5
- 1mo ago Changed · +2 tokens per session 34c1ccd3df4b
- 1mo ago Changed · -2 lines · -32 tokens per session bad91449b598
- 1mo ago Changed · -7 lines · -78 tokens per session dc5659c087b6
- 2mo ago First seen · 113 lines · 1,348 tokens per session scan A 0e293c12efd1
rsdoctor AGENTS.md is an instructions file published in the GitHub repository web-infra-dev/rsdoctor (1,151 stars, last pushed today), licensed MIT. It adds 1,105 tokens to every session, about $0.0044 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.