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/monorepogit 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/monorepo)<a href="https://agentmods.dev/rules/nedcodes-ok/cursorrules-collection/monorepo"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursorrules-collection/monorepo.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.00476 | $0.00476 |
| Opus 5 | $0.00238 | $0.00238 |
| Sonnet 5 | $0.00095 | $0.00095 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
monorepo 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.
How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monorepo Cursor Rules
You are an expert in monorepo architecture. Follow these rules:
Workspace Structure
- Use a flat packages/ or apps/ + packages/ layout — max one level of nesting
- Each package has its own package.json/pyproject.toml with explicit dependencies
- Shared code goes in packages/ — apps consume packages, never import across apps
- Every package must build independently — no reliance on root-level config
Dependency Management
- Use workspace protocol for internal deps: "workspace:*" (pnpm/yarn) or file: references
- Hoist shared devDependencies to root — keep runtime deps in each package
- Pin external dependency versions at root to prevent drift across packages
- Use a lockfile at root — never per-package lockfiles
Boundaries
- Never import from another app — apps are deployment units, not libraries
- Shared types/utils go in a dedicated package (e.g., @repo/shared, @repo/types)
- Enforce boundaries with ESLint import rules or turborepo/nx task dependencies
- Each package declares its public API via exports field or index.ts — no deep imports
Build & Tasks
- Use Turborepo, Nx, or similar for task orchestration with caching
- Define task dependencies: build depends on ^build (build deps first)
- Use --filter to run tasks for changed packages only: turbo run build --filter=...[HEAD~1]
- Cache build outputs — never rebuild unchanged packages in CI
CI/CD
- Run affected-only tests: only test packages changed in the PR
- Use separate deploy pipelines per app — never deploy all apps on every merge
- Validate the entire dependency graph in CI: no circular deps, no missing deps
- Use changesets or similar for coordinated versioning and changelogs
Code Sharing Patterns
- Extract shared logic only when used by 3+ consumers — premature sharing creates coupling
- Version internal packages at 0.x until stable — breaking changes are expected
- Shared configs (ESLint, TypeScript, Prettier) go in a @repo/config package
- Use TypeScript project references or composite builds for cross-package type checking
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 · 45 lines · 476 tokens per session scan A ef3fdba3f30b
monorepo is a cursor rule published in the GitHub repository nedcodes-ok/cursorrules-collection (37 stars, last pushed 6mo ago), licensed MIT. It adds 476 tokens to every session, about $0.0024 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
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.
ai-dev-os-ticket
Generates a ticket (local file or GitHub Issue) with implementation summary and checklist candidates derived from AI Dev OS guidelines. Used to create structured implementation tasks.
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.
03-ui
UI, layout, theming and localization standards.