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/skills/draft-security-advisory/SKILL.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/skills/nrwl/nx/draft-security-advisory)<a href="https://agentmods.dev/skills/nrwl/nx/draft-security-advisory"><img src="https://agentmods.dev/badge/skills/nrwl/nx/draft-security-advisory/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/skills/nrwl/nx/draft-security-advisory"><img src="https://agentmods.dev/badge/skills/nrwl/nx/draft-security-advisory.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.00115 | $0.01717 |
| Opus 5.5 | $0.00046 | $0.00687 |
| Sonnet 5.5 | $0.00023 | $0.00343 |
| Haiku 4.5 | $0.00012 | $0.00172 |
Grade A, and why
draft-security-advisory 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 3d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Draft Security Advisory (draft-security-advisory)
Turn a vulnerability report into a ready-to-review GitHub security advisory draft
for nrwl/nx. This skill drafts; it NEVER publishes. The final review and the
publish step are always performed by a human.
Save the finished draft to tmp/security-advisories/<slug>/advisory.md (gitignored),
where <slug> is a short kebab-case name for the vulnerability
(e.g. graph-server-cors).
Inputs
The argument is the vulnerability report: a file path, pasted text, or a pointer
(e.g. a GitHub private vulnerability report / GHSA draft ID, fetchable via
gh api /repos/nrwl/nx/security-advisories/<GHSA-ID>). If no report is provided,
ask for one — do not invent a vulnerability.
Process
Work through these phases in order. Do not skip the investigation phases — the advisory must be grounded in the actual code, not just the reporter's claims.
Phase 1 — Understand the report
- Read the full report. Identify: the claimed flaw, the attack scenario, the entry point (which package / command / server), and any proof of concept.
- Restate the vulnerability in one sentence before proceeding. If the report is ambiguous or you cannot confirm the flaw exists in the code, stop and report that instead of drafting.
Phase 2 — Confirm scope in the code
- Locate the vulnerable code in this repo. Read enough surrounding code to understand the real trust boundary: what is attacker-controlled, what checks exist, and what the worst-case outcome is.
- Determine what is and is not exposed. Which configurations, commands, or
product surfaces trigger the vulnerable path? Which ones use a different code
path and are unaffected? This is a per-report judgment based on the code you
just read — verify each claim of "not affected" by finding the diverging code
path, and say so in the draft with a
> [!IMPORTANT]callout. - Distinguish "practical impact in realistic usage" from "theoretical worst case" — the Summary states the practical impact; the Details section may note the escalation path.
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.
- 3d ago First seen · 154 lines · 115 tokens per session scan A f9545610b2d0
draft-security-advisory is a skill published in the GitHub repository nrwl/nx (29,416 stars, last pushed today), licensed MIT. It adds 115 tokens to every session and 1,717 once invoked, about $0.0005 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-10-20.
Other skills, from other repositories
Cypress v14 Component Testing
Component testing patterns with Cypress v14 including React, Vue, and Angular component mounting, custom mount commands, interaction testing, visual snapshots, and integration with Vite and Webpack bundlers.
framework-nextjs
Guides Next.js work under the Next.js standard: deciding server or client before writing a component, declaring cache behaviour before a fetch, treating each server action as a public endpoint, and testing at each framework boundary.
framework-react
Guides React state, effects, and data work under the React standard: finding each value's narrowest home, deciding whether an effect is needed at all, keeping server data in the query cache, and testing hooks and data flows.
merge-seed
Merge upstream React Starter Kit updates (the seed remote) into main, preserving this project's identity, scope, and behavior. Use when asked to sync, pull, or merge the seed / starter kit / upstream template.
getting-started
Get started with your Open SaaS project — fetches docs, checks Wasp installation, and helps you start your database and app.
guided-tour
Take a guided tour of Open SaaS — walks you through step-by-step through the project structure, features, and customization checklist.