Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/giselles-ai/giselleWrote 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/rules/giselles-ai/giselle/nodejs)<a href="https://agentmods.dev/rules/giselles-ai/giselle/nodejs"><img src="https://agentmods.dev/badge/rules/giselles-ai/giselle/nodejs/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/rules/giselles-ai/giselle/nodejs"><img src="https://agentmods.dev/badge/rules/giselles-ai/giselle/nodejs.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.00003 | $0.00444 |
| Opus 5.5 | $0.00001 | $0.00178 |
| Sonnet 5.5 | $0.00001 | $0.00089 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade C, and why
nodejs 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 1mo 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.
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.2/install.sh | bash Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.2/install.sh | bash Copies of this mod
1 near-identical copy found in the catalogue:
- nodejs — 100% identical, 0 lines differ
What it actually says
Setting up Node.js with NVM and pnpm
This guide will walk you through installing Node.js using NVM (Node Version Manager) and setting up pnpm as your package manager.
Installing Node Version Manager (NVM)
NVM allows you to install and manage multiple versions of Node.js on your system.
macOS and Linux
- Install NVM by running the following command in your terminal:
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.2/install.sh | bash
Or using wget:
wget -qO- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.2/install.sh | bash
-
Close and reopen your terminal to load NVM.
-
Verify NVM is installed correctly:
nvm --version
Installing Node.js
Giselle requires Node.js version 22.14.0 or later.
- Install the required Node.js version:
nvm install 22.14.0
- Set this version as default:
nvm use 22.14.0
- Verify the installation:
node --version
The output should show v22.14.0 or later.
Setting up pnpm
pnpm is a fast, disk space efficient package manager that's used by the Giselle project.
- Install pnpm using the recommended method:
curl -fsSL https://get.pnpm.io/install.sh | sh -
-
Close and reopen your terminal to load pnpm.
-
Verify pnpm is installed correctly:
pnpm --version
Troubleshooting
If you encounter any issues:
- Make sure your terminal is restarted after installing NVM
- Check that you're using the correct Node.js version with
node --version - Ensure pnpm is installed globally with
pnpm --version - If commands aren't recognized, verify your PATH environment variables
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.
- 1mo ago First seen · 86 lines · 3 tokens per session scan C b6543bb83838
nodejs is a cursor rule published in the GitHub repository giselles-ai/giselle (558 stars, last pushed 18d ago), licensed Apache-2.0. It adds 3 tokens to every session and 444 once invoked, about $0.0000 per session on Opus 5.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 cursor rules, from other repositories
ipynb-files
This file contains rules and prompts for handling Jupyter Notebook (.ipynb) files in Cursor IDE, which currently doesn't have native support for .ipynb files.
expo
Expo Development Standards.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.