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/nedcodes-ok/cursorrules-collectionWrote 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/nedcodes-ok/cursorrules-collection/pnpm)<a href="https://agentmods.dev/rules/nedcodes-ok/cursorrules-collection/pnpm"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursorrules-collection/pnpm/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/nedcodes-ok/cursorrules-collection/pnpm"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursorrules-collection/pnpm.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.00365 | $0.00365 |
| Opus 5.5 | $0.00146 | $0.00146 |
| Sonnet 5.5 | $0.00073 | $0.00073 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
pnpm 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 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.
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.
What it actually says
PNPM Rules
Workspace Setup
- Use pnpm-workspace.yaml to define workspace packages
- Structure as
packages/*or organized by type:apps/*,packages/*,tools/* - Use workspace protocol (workspace:) for internal dependencies
- Configure shared dependencies in root package.json
- Use workspace filtering with --filter flag for targeted operations
Package Management
- Use exact versions for critical dependencies
- Leverage peer dependencies for shared libraries
- Use .pnpmrc for consistent configuration across team
- Configure node-linker=hoisted only when absolutely necessary
- Use shamefully-hoist=false for strict dependency isolation
Scripts & Commands
- Define common scripts in root package.json for workspace-wide operations
- Use
pnpm -rfor recursive operations across all packages - Use
pnpm --filterfor selective package operations - Create turbo.json or nx.json for build orchestration
- Use pre/post hooks for lifecycle management
Performance
- Use .pnpmrc to configure store-dir for optimal disk usage
- Enable verify-store-integrity=false for faster installs in CI
- Use frozen-lockfile=true in production environments
- Configure registry mirrors for private packages
- Use node_modules structure understanding for debugging
Monorepo Best Practices
- Keep package versions synchronized using workspace ranges
- Use shared ESLint, TypeScript configs from workspace packages
- Configure path mapping in TypeScript for internal packages
- Use consistent naming convention for internal packages (@scope/package-name)
- Separate publishable packages from private workspace tools
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 · 42 lines · 365 tokens per session scan A acda5893d4ee
pnpm is a cursor rule published in the GitHub repository nedcodes-ok/cursorrules-collection (38 stars, last pushed 7mo ago), licensed MIT. It adds 365 tokens to every session, about $0.0015 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-09-03.
Other cursor rules, from other repositories
23-app-startup
Application class, SplashScreen, StartupActivity + MainActivity split, and AndroidX Startup.
03-android-architecture
Clean Architecture layer rules.
12-naming-conventions
Cross-cutting naming conventions reference — Kotlin, Gradle, packages, resources, logging, analytics, domain.
01-feature-checklist
New feature / screen scaffolding checklist — use when adding a feature, sonic-create-screen, sonic-create-mvi, sonic-create-clean-architecture, or verifying a feature is complete.
06-coroutines-flow
Coroutines, Flow, dispatchers, ANR prevention, large datasets.
08-gradle
Gradle, build config, catalog sections/naming, and dependency management.