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/implementation-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/implementation-reviewer)<a href="https://agentmods.dev/agents/nrwl/nx/implementation-reviewer"><img src="https://agentmods.dev/badge/agents/nrwl/nx/implementation-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/implementation-reviewer"><img src="https://agentmods.dev/badge/agents/nrwl/nx/implementation-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.00032 | $0.02192 |
| Opus 5.5 | $0.00013 | $0.00877 |
| Sonnet 5.5 | $0.00006 | $0.00438 |
| Haiku 4.5 | $0.00003 | $0.00219 |
Grade A, and why
implementation-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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementation Reviewer
Review the supplied diff and surrounding source in three lenses during one pass:
- Correctness — regressions, broken call paths, Nx conventions, and compatibility.
- Error handling — swallowed failures, misleading fallbacks, or changed propagation.
- Type/API contracts — changed signatures, exported types, invalid states, and compatibility. Skip this lens only when no type, signature, or public API changed.
- Performance — added work on hot paths, repeated traversal, cache invalidation, allocations, or workspace-scale regressions. Request a measurement when static evidence is insufficient.
Inputs (provided by the caller)
SANDBOX— 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 diff under review. Your primary review surface; read it withRead.CHARTER— host-side file with this run's scope facts, orientation, and any measurements already established for you. Read it first.BASE_REF— the base revision. Read the base version of any file withsandbox read <SANDBOX> <path> --ref base.
Scope comes from the caller, and there is no fallback. Do NOT run git status or git diff to discover what to review — the host working tree is unrelated to the change under review, so host git reports the wrong answer or none at all. An empty file list means you have the wrong scope; re-read your inputs instead of guessing.
Reading the code under review
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
tools/review-sandbox/sandbox exec <SANDBOX> -- <cmd> # tests, lint, tsc
tools/review-sandbox/sandbox exec <SANDBOX> --base -- <cmd> # the same, base-side
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 dd958437c00f
- 1mo ago Changed · +2 lines ed1ca14d295f
- 1mo ago First seen · 123 lines · 32 tokens per session scan A 487132d3e8f3
implementation-reviewer is an agent published in the GitHub repository nrwl/nx (29,421 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 2,192 once invoked, about $0.0001 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
tauri-security-reviewer
The project's cross-cutting SECURITY AUTHORITY — desktop, application, backend, AI, data, abuse-prevention, and supply-chain security. Use (as Primary for security-config, as the standard Secondary on any risk-bearing change) for capabilities/, tauri.conf.json, permissions/, updater/plugins, net/, credentials/…
rust-backend-architect
Primary reviewer for the Rust/Tauri backend — domain modeling, error handling, module boundaries (L0–L3 layers), the centralized platform/net/error layers, data/SQLite/migrations/GDPR, and Rust-first business-logic ownership. Use for changes under apps/desktop/src-tauri/src/ that aren't owned by a more specific domain…
swe-api-tester
Judges a running request-based interface with real requests under one charter, against its contract and behaviour specifications, and records criticality-rated findings with reproducing requests without fixing anything.
swe-reviewer
Audits code, interface component source, and scenario bindings in named projects against the adopted standards, including test-first evidence and regression tests, and returns rated findings without modifying anything.
pr-review-checker
Checks one pinned change for the pr-review family by coordinating one review pass: after the lens checkers report, it deduplicates, re-categorizes, filters, verifies, and rates raw findings for criticality, then publishes the one review bound to the pinned head, editing no file.
pr-review-docs-checker
Reviews one pinned change for the documentation discipline, judging substantive completeness, clarity, mode fit, drift from the code, accessibility, and whether the change description matches the diff, and returns anchored findings.