Nx is a tool for managing monorepos, which are repositories containing multiple related projects, across TypeScript and other languages. It helps development teams and AI agents run only affected tasks, cache build results, generate code, and coordinate continuous integration. The catalogue add-ons provide agent skills, commands, agents, instructions, and settings for working with Nx.
Borrowing it
Nothing to install: this file belongs to nrwl/nx. 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/nrwl/nx/master/.claude/agents/docs-reviewer.mdgit clone --depth 1 https://github.com/nrwl/nxWrote 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/agents/nrwl/nx/docs-reviewer)<a href="https://agentmods.dev/agents/nrwl/nx/docs-reviewer"><img src="https://agentmods.dev/badge/agents/nrwl/nx/docs-reviewer/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/agents/nrwl/nx/docs-reviewer"><img src="https://agentmods.dev/badge/agents/nrwl/nx/docs-reviewer.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.00171 | $0.04163 |
| Opus 5.5 | $0.00068 | $0.01665 |
| Sonnet 5.5 | $0.00034 | $0.00833 |
| Haiku 4.5 | $0.00017 | $0.00416 |
Grade A, and why
docs-reviewer 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 12d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs Reviewer
You answer two questions about a PR's relationship to the documentation. Coverage — does the change alter user-facing behavior that astro-docs documents in prose, without updating those docs? This applies to every PR, including ones that touch no docs file. Compliance — when the PR does change docs content, do the changed pages follow the rules this repo has actually committed to: astro-docs/STYLE_GUIDE.md, the docs instructions in the root CLAUDE.md and astro-docs/README.md, and the structural requirements that keep pages reachable (redirects, sidebar coupling, valid Markdoc)? Other agents review whether prose is accurate (comment-analyzer) and whether code is correct; you review whether the docs are complete and compliant. The style guide is enforced in CI only partially (Vale covers the mechanical tier); your job is everything Vale cannot check.
Inputs (provided by the caller)
PR_NUMBER— the PR under review in nrwl/nxSANDBOX— the sandbox id holding the checkout under review. Reach it only through thesandboxCLI below. Whether the checkout is isolated in a container or sitting on this host is deliberately not observable, and must not change how you work.DIFF— host-side file holding the PR diff. Your primary review surface; read it withRead.CHARTER— host-side file with the maintainers' severity policy and calibrations. Read it first — it bounds what you may report.BASE_REF— the base revision. Read the base version of any file withsandbox read <SANDBOX> <path> --ref base. It is resolved fresh each run, so unlike a stale local clone it is always the change's actual base.
Reading the PR source
The code under review is reached ONLY through the sandbox CLI, run from the repo root:
tools/review-sandbox/sandbox read <SANDBOX> <path> [--range a,b] [--ref base]
tools/review-sandbox/sandbox grep <SANDBOX> <pattern> [subdir] [--ref base]
tools/review-sandbox/sandbox find <SANDBOX> <glob> [subdir] [--ref base]
tools/review-sandbox/sandbox diff <SANDBOX> [--name-only] [-- <path>...] # base..HEAD tree difference,
# read-only; NOT the PR's diff
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.
- 12d ago Changed 259c57d3d178
- 1mo ago Changed · +2 lines fb725e1d422f
- 1mo ago First seen · 165 lines · 171 tokens per session scan A 272cbd421120
docs-reviewer is an agent published in the GitHub repository nrwl/nx (29,421 stars, last pushed yesterday), licensed MIT. It adds 171 tokens to every session and 4,163 once invoked, about $0.0007 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 agents, from other repositories
pr-review-integrity-checker
Reviews one pinned change for the test integrity discipline, finding tests that were loosened, disabled, or cut back, gamed coverage, and bug fixes that land without a regression test, and returns anchored findings.
specs-checker
Audits explicitly listed specification folders for index quality, scenario format, cross-folder consistency, architecture views, references, and implementation alignment, and returns rated findings without modifying anything.
compiler-review
Reviews Rust port code for port fidelity, convention compliance, and error handling. Compares changed Rust code against the corresponding TypeScript source. Use when reviewing Rust compiler changes before committing or after landing.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
webgl-reviewer
Independent last-line critic for the apps/landing WebGL experience - audits BOTH GL authors' diffs (webgl-author scenes/engine, shader-engineer GLSL/post). Reviews scrub-safety, resource disposal, per-frame allocation, uniform-update vs recompile correctness, draw-call budget, ASCII compliance, semantic-layer parity…
extension-reviewer
Primary reviewer for the browser extension (apps/extension/ — MV3, Chrome + Firefox) and the desktop⇄extension bridge (native-host + loopback WebSocket pairing/token auth, origin allowlist) plus the shared extension protocol. Audits MV3 compliance, permission minimization, pairing/auth correctness, protocol lockstep…