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.
npx agentmods add rules/nedcodes-ok/cursorrules-collection/turborepogit 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/turborepo)<a href="https://agentmods.dev/rules/nedcodes-ok/cursorrules-collection/turborepo"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursorrules-collection/turborepo.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 | $0.00634 | $0.00634 |
| Opus 5 | $0.00317 | $0.00317 |
| Sonnet 5 | $0.00127 | $0.00127 |
| Haiku 4.5 | $0.00063 | $0.00063 |
Grade A, and why
turborepo 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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- turborepo — 100% identical, 0 lines differ
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.
Turborepo Cursor Rules
You are an expert in Turborepo monorepo management. Follow these rules:
Project Structure
- Apps in apps/: apps/web, apps/api, apps/docs
- Shared packages in packages/: packages/ui, packages/config, packages/utils
- Each package has its own package.json with a "name" field matching the directory
- Use workspace protocol for internal deps: "@repo/ui": "workspace:*"
- Root package.json only for dev tooling (turbo, prettier, lint-staged)
turbo.json Configuration
- Define all tasks in turbo.json pipeline, not in package.json scripts alone
- Set correct dependsOn: build depends on ^build (upstream packages first)
- Mark dev tasks with "persistent": true and "cache": false
- Set outputs correctly: build → ["dist/", ".next/"], lint → [] (no outputs)
- Use inputs to scope cache: lint inputs should include ["src/**", ".eslintrc.*"]
Caching
- Never disable caching without a reason — it's Turbo's main value
- Use Remote Caching (Vercel or self-hosted) for CI speed
- Add .turbo to .gitignore
- Set env vars that affect output in turbo.json globalEnv or task env
- If builds differ between environments, the env var must be in globalEnv
Task Pipelines
- Lint and type-check don't need ^build unless they import built output
- Test tasks: dependsOn: ["build"] if tests use built artifacts, [] otherwise
- Use turbo run build --filter=web to target specific apps
- Use --dry to verify what Turbo will execute before long runs
Shared Packages
- Export via package.json "exports" field with proper conditions (import, require, types)
- Use "main" and "types" for backward compat alongside "exports"
- Shared tsconfig in packages/config/tsconfig: base.json, nextjs.json, react-library.json
- Shared ESLint config in packages/config/eslint
Anti-Patterns — Do NOT
- ❌ Installing dependencies in the root that belong in a specific workspace
- ❌ Circular dependencies between packages — Turbo will error or produce wrong order
- ❌ Hard-coding paths to sibling packages — use workspace deps
- ❌ Putting source code in the root — all code lives in apps/ or packages/
- ❌ Caching tasks with side effects (deploy, db:push) — mark them "cache": false
- ❌ Using npm/yarn workspaces features that conflict with Turbo's task runner
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.
- yesterday First seen · 57 lines · 634 tokens per session scan A db225f7fbacd
turborepo is a cursor rule published in the GitHub repository nedcodes-ok/cursorrules-collection (37 stars, last pushed 6mo ago), licensed MIT. It adds 634 tokens to every session, about $0.0032 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-09-03.
Other cursor rules, from other repositories
90-devops-deployment
Docker, CI/CD, AWS, Vercel, and VPS deployment rules.
pipeline
Full CI pipeline — typecheck, lint, build, test, security, report.
10-feature-development
Feature implementation workflow and engineering mindset.
11-template-conventions
Reusable building blocks shipped with this template - use them instead of writing new ones.
12-new-project
Workflow for starting a new app from this template - rebranding, identity, cleanup and first feature.
13-updating-project
Workflow for updating an existing project - dependency and SDK upgrades, migrations, refactors, bug fixes.