What is nx-ai-agents-config CLAUDE.md?

Project instructions for working with Nx, a tool for managing multiple related applications and libraries in one code workspace.

Use them when working in Nx projects, inspecting the project graph, running affected tasks, checking project details, or writing agent instructions in the repository.

They guide an AI assistant to understand the workspace and use Nx commands and tools consistently for builds, tests, linting, and configuration questions.

How nrwl/nx-ai-agents-config configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to nrwl/nx-ai-agents-config. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/nrwl/nx-ai-agents-config/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/nrwl/nx-ai-agents-config

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/nrwl/nx-ai-agents-config/claude-md/github.svg)](https://agentmods.dev/instructions/nrwl/nx-ai-agents-config/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/nrwl/nx-ai-agents-config/claude-md"><img src="https://agentmods.dev/badge/instructions/nrwl/nx-ai-agents-config/claude-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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/nrwl/nx-ai-agents-config/claude-md"><img src="https://agentmods.dev/badge/instructions/nrwl/nx-ai-agents-config/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 853 This file is loaded in full into every session.

When invoked 853 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00853	$0.00853
Opus 5	$0.00426	$0.00426
Sonnet 5	$0.00171	$0.00171
Haiku 4.5	$0.00085	$0.00085

Measured 10d ago against content hash cbd6e89479d0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

nx-ai-agents-config CLAUDE.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 10d 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.

CLAUDE.md · 74 lines

How it starts

The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.

General Guidelines for working with Nx

When running tasks (for example build, lint, test, e2e, etc.), always prefer running the task through nx (i.e. nx run, nx run-many, nx affected) instead of using the underlying tooling directly
You have access to the Nx MCP server and its tools, use them to help the user
When answering questions about the repository, use the nx_workspace tool first to gain an understanding of the workspace architecture where applicable.
When working in individual projects, use the nx_project_details mcp tool to analyze and understand the specific project structure and dependencies
For questions around nx configuration, best practices or if you're unsure, use the nx_docs tool to get relevant, up-to-date docs. Always use this instead of assuming things about nx configuration
If the user needs help with an Nx configuration or project graph error, use the nx_workspace tool to get any errors

When writing regular skills and agents in this repo (in /artifacts), always use agent-agnostic language. There are many different ways of representing MCP tool formats, different default subagents et cetera. Since we generally support all these subagents from the same source files, always use descriptions that will make sense for different coding agents. Don't do this: "Use the mcp__nx-mcp__ci_information MCP tool" Do this instead: "Use the ci-information tool from the nx MCP server" (you don't always have to mention the mcp server if it's obvious)

Self-healing CI

If the artifact sync verification task fails, fix it by running the sync artifacts script (npx nx sync-artifacts)

Building Artifacts

This repository generates extensibility artifacts (commands, skills, subagents) for multiple AI agents.

Run npx nx sync-artifacts to generate outputs for all agents
One plugin is built from this repo: nx, with source in artifacts/ and output to the repo root (skills/, agents/, .mcp.json) and generated/
Generated files:
- Claude Code and Cursor plugins share output: skills/, agents/, .mcp.json
  - Claude plugin manifest: .claude-plugin/plugin.json
  - Cursor plugin manifest: .cursor-plugin/plugin.json (uses convention-based discovery of root skills/ and agents/)
- Other agents output to generated/:
  - .opencode/ - OpenCode
  - .github/ - GitHub Copilot
  - .cursor/ - Cursor
  - .gemini/ - Gemini
  - .agents/ - Codex (skills only)
  - .codex/ - Codex (MCP config)
The plugin is registered in .claude-plugin/marketplace.json

Read the full file on GitHub · 74 lines

Changes

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.

10d ago First seen · 74 lines · 853 tokens per session scan A cbd6e89479d0

Subscribe to this mod's changes

nx-ai-agents-config CLAUDE.md is an instructions file published in the GitHub repository nrwl/nx-ai-agents-config (28 stars, last pushed 1mo ago), licensed MIT. It adds 853 tokens to every session, about $0.0043 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.

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.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

nx-ai-agents-config: Instructions file for Claude Code