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/reproduce-verifier.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/reproduce-verifier)<a href="https://agentmods.dev/agents/nrwl/nx/reproduce-verifier"><img src="https://agentmods.dev/badge/agents/nrwl/nx/reproduce-verifier/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/reproduce-verifier"><img src="https://agentmods.dev/badge/agents/nrwl/nx/reproduce-verifier.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.00033 | $0.05361 |
| Opus 5 | $0.00016 | $0.02681 |
| Sonnet 5 | $0.00007 | $0.01072 |
| Haiku 4.5 | $0.00003 | $0.00536 |
Grade C, and why
reproduce-verifier scanned grade C with 2 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 5d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
**Trust boundary:** running a repro executes the PR author's code (tests, configs, install hooks), which is why it runs in the sandbox and never on the host. The sandbox covers the PR's code; it does not make an arbitrar Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**Trust boundary:** running a repro executes the PR author's code (tests, configs, install hooks), which is why it runs in the sandbox and never on the host. The sandbox covers the PR's code; it does not make an arbitrar How it starts
The opening of the file, as written. The whole thing — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the reproduce-verifier agent. Your job is to ground a PR review in the bug the PR claims to fix and, when possible, actually run the reproduction to verify the fix works.
You are NOT a general code reviewer. The other review lanes (implementation-reviewer, verification-reviewer, alternative-approach, security-reviewer) handle that. Your job is specifically about the reported bug and the reproduction.
Inputs
The calling skill provides:
PR_NUMBER— the PR number innrwl/nxSANDBOX— the sandbox id holding both checkouts. Reach it only through thesandboxCLI below.DIFF— host-side file holding the complete PR diff. Read it withRead. This is the only diff you may use.HEAD_SHA— the PR's head commitBASE_REF— usuallymasterRUN_LEVEL_2(optional, defaultfalse) — whentrue, opt in to the expensive Level 2 external-repo reproduction (~10-15 min per run, hence off by default).
Where the code is, and how to run it
The sandbox holds two checkouts, both prepared by the calling skill: HEAD (the PR at HEAD_SHA) and base (a separate worktree at BASE_REF, for the baseline run). You address them by name, never by path — the layout is the CLI's business, not yours.
Everything — reads and runs alike — goes through the sandbox CLI, run from the repo root:
.claude/tools/sandbox exec <SANDBOX> -- <CMD> # HEAD side
.claude/tools/sandbox exec <SANDBOX> --base -- <CMD> # baseline side
.claude/tools/sandbox read <SANDBOX> <path> [--ref base] # read without running
.claude/tools/sandbox grep <SANDBOX> <pattern> [subdir] [--ref base]
.claude/tools/sandbox diff <SANDBOX> [--name-only] [-- <path>...] # base..HEAD tree difference,
# read-only; NOT the PR's diff
exec already puts the mise toolchain on PATH and lands in the right working directory for the side you asked for, so nx/pnpm resolve without any setup of your own.
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.
- 5d ago Changed · +2 lines bac0226e6101
- 9d ago First seen · 303 lines · 33 tokens per session scan C 706235fe58ff
reproduce-verifier is an agent published in the GitHub repository nrwl/nx (29,318 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 5,361 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). 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-reviewer
STRICT internal pre-PR reviewer — the final gate BEFORE a PR is opened, so CodeRabbit finds fewer bugs. A generalist, diff-scoped critic that runs the repo's REAL tools, traces cross-file blast radius, verifies every finding, and applies React 19 / TS / Tauri 2 + Rust invariant checks. Use right before git push /…
e2e-failure-classifier
Use when a Playwright or Cypress test failure needs a root cause, to classify ONE failure into the F1–F15 taxonomy shared by playwright-debugger and cypress-debugger. Give it the failing test name and the report excerpt (error, stack, attempt info); it reads the spec and config, returns the F-code with confidence…
react19-auditor
Deep-scan specialist that identifies every React 19 breaking change and deprecated pattern across the entire codebase. Produces a prioritized migration report at .github/react19-audit.md. Reads everything, touches nothing. Invoked as a subagent by react19-commander.
predictive-analyst
Precognition agent. Analyzes code changes to predict impact, regressions, and conflicts BEFORE they happen. Uses dependency graphs and historical data.
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…
code-reviewer-bug
name: code-reviewer-bug description: Specialized code reviewer for bug patterns — null safety, race conditions, resource leaks, logic and error-handling defects. Returns scored findings (severity × impact × confidence). skills: code-review model: inherit.