@aws/nx-plugin is a collection of Nx code generators that creates full-stack applications and their AWS deployment infrastructure inside an Nx monorepo, a single workspace containing multiple related projects. It is used by developers building TypeScript, Python, and React applications with AWS services. The catalogue entries support using and extending the plugin through its workflows and integrations.
Borrowing it
Nothing to install: this file belongs to awslabs/nx-plugin-for-aws. 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/awslabs/nx-plugin-for-aws/main/CLAUDE.mdgit clone --depth 1 https://github.com/awslabs/nx-plugin-for-awsWrote 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/awslabs/nx-plugin-for-aws/claude-md)<a href="https://agentmods.dev/instructions/awslabs/nx-plugin-for-aws/claude-md"><img src="https://agentmods.dev/badge/instructions/awslabs/nx-plugin-for-aws/claude-md.svg" alt="Measured on agentmods" 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.00520 | $0.00520 |
| Opus 5 | $0.00260 | $0.00260 |
| Sonnet 5 | $0.00104 | $0.00104 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
nx-plugin-for-aws 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 2d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instructions for Claude
Required Reading
Read the following before making changes:
- CONTRIBUTING.md — the authoritative guide for generator idempotency, testing expectations, writing documentation, and the PR process.
- Contributing a Generator tutorial — how to build a generator end to end, including working backwards from a real project to inform the generator changes.
Commands
Install dependencies:
pnpm i
Build:
pnpm nx run-many --target build --all
Run tests and update snapshots:
pnpm nx run @aws/nx-plugin:test -u
Tips
- Always use
npx -y(not barenpx) to avoid the "Ok to proceed?" prompt hanging in non-interactive environments.
Code Style
- Keep comments succinct and always describe the current state — never include historical context or changelog-style notes.
- Comments in generated/template files should be minimal.
- Use the existing codebase to inform code style, testing style, etc.
Testing Changes End-to-End
Before raising a PR, validate changed generators in an example workspace using locally compiled versions:
- Consult the Nx Plugin for AWS MCP server (
create-workspace-command,list-generators,generator-guide,general-guidance) as the baseline for creating workspaces and running generators. Expect deviations driven by the local changes under test. - Make the locally compiled packages available to the workspace — either publish them to a local Verdaccio registry, or use
pnpm link. - Create a fresh workspace, then invoke the relevant changed generators with the locally compiled versions.
- Confirm everything builds and runs locally, including the
devtarget. - If the change warrants it, deploy to AWS, test there, then tear down all provisioned resources.
Best Practices
- Always ensure the build passes before raising a PR.
- Update snapshots if there are failures due to snapshot changes.
- Use conventional commits, referencing the generator you are working on, eg "feat(ts#project): my commit message". Use the
depstype for bumping dependency versions vended to users — see Commit Messages for the type-to-release-bump mapping. - Raise PRs following the PR template.
- After pushing to a PR, monitor the checks and iterate on any failures until all are green.
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.
- 2d ago Changed · +41 tokens per session a6f95b0757c1
- 7d ago First seen · 57 lines · 479 tokens per session scan A 5f9721529ea6
nx-plugin-for-aws CLAUDE.md is an instructions file published in the GitHub repository awslabs/nx-plugin-for-aws (95 stars, last pushed yesterday), licensed Apache-2.0. It adds 520 tokens to every session, about $0.0026 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.
Other instructions, from other repositories
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.
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).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
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.
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.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.