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/cursor-doctorWrote 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/cursor-doctor/turborepo)<a href="https://agentmods.dev/rules/nedcodes-ok/cursor-doctor/turborepo"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursor-doctor/turborepo/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/cursor-doctor/turborepo"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursor-doctor/turborepo.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.00634 | $0.00634 |
| Opus 5.5 | $0.00254 | $0.00254 |
| Sonnet 5.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 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.
This is a copy
100% identical to turborepo — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 1mo ago First seen · 57 lines · 634 tokens per session scan A db225f7fbacd
turborepo is a cursor rule published in the GitHub repository nedcodes-ok/cursor-doctor (10 stars, last pushed 7mo ago), licensed MIT. It adds 634 tokens to every session, about $0.0025 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to turborepo, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
test-patterns
Selenium pytest test patterns — data-driven tests, fixtures, error handling, and performance checks.
testing-fundamentals
Core Cypress testing principles — selector strategy, smart waiting, and spec organization. Apply when writing or reviewing Cypress E2E tests.
web
Web build conventions (separate from native and RN JS).
components
Component patterns and UI conventions.
git
Git workflow and commit conventions.
minimax-m3-self-evolution
MiniMax M3 self-evolution harness: iterative refinement loops, compress-before-iterate, autonomous debugging, and recursive improvement patterns.