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/louisbrulenaudet/monorepo-templateWrote 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/louisbrulenaudet/monorepo-template/turborepo)<a href="https://agentmods.dev/rules/louisbrulenaudet/monorepo-template/turborepo"><img src="https://agentmods.dev/badge/rules/louisbrulenaudet/monorepo-template/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/louisbrulenaudet/monorepo-template/turborepo"><img src="https://agentmods.dev/badge/rules/louisbrulenaudet/monorepo-template/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.00544 | $0.00544 |
| Opus 5 | $0.00272 | $0.00272 |
| Sonnet 5 | $0.00109 | $0.00109 |
| Haiku 4.5 | $0.00054 | $0.00054 |
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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Turborepo Query & Remote Cache
Read-only graph primitives and signed-cache provisioning for this repo's turbo setup. Task/pipeline semantics live in root turbo.json comments and core/boundaries; CI invariants live in ops/ci.
Turbo query (agent primitives)
turbo query is the read-only way to inspect the graph without running tasks - prefer it over speculative dry runs:
| Command | Use |
|---|---|
turbo query affected |
Which tasks are affected by working-tree changes (JSON by default) |
turbo query affected --tasks build |
Same, scoped to one task name |
turbo query affected --packages |
Affected packages instead of tasks |
turbo query ls [pkg] |
Package list / per-package deps and tasks |
turbo query --schema |
GraphQL schema to load before writing custom queries |
Remote cache
Remote caching is enabled and signed (remoteCache.signature: true, longerSignatureKey). Local dev and CI need TURBO_REMOTE_CACHE_SIGNATURE_KEY (>= 32 bytes) alongside TURBO_TOKEN/TURBO_TEAM, or signed fetches fail closed. Without the key set locally, expect remote-cache misses; local caching is unaffected. Rotation invalidates every previously signed artifact - one rebuild per task, then the cache re-populates.
Provisioning a dev machine
CI gets TURBO_TOKEN / TURBO_TEAM / TURBO_REMOTE_CACHE_SIGNATURE_KEY from repo secrets (.github/workflows/*.yml); a dev machine gets nothing automatically. Either run turbo login && turbo link, or export all three in the shell profile - the signature key must be the same >= 32-byte value CI uses, and none of them may ever be committed. Verify with a task CI already built: a remote hit logs cache hit, replaying logs on a cold local cache. A machine without them runs local-cache-only by design - correct, just slower.
Constrained machines
On small hardware (4 cores / <4 GB RAM), prefer --concurrency=2 on heavy graphs (pnpm turbo run check-types test build --concurrency=2) to limit memory pressure from parallel tsc/vitest/vite. Guidance only - never lower concurrency in turbo.json; that would slow CI runners.
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.
- 12d ago First seen · 34 lines · 544 tokens per session scan A dea09027c2cc
turborepo is a cursor rule published in the GitHub repository louisbrulenaudet/monorepo-template (19 stars, last pushed 11d ago), licensed Apache-2.0. It adds 544 tokens to every session, about $0.0027 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-08-30.
Other cursor rules, from other repositories
paperfit
PaperFit project rule for LaTeX visual typesetting optimization.
swift-argument-parser
Documentation and usage patterns for Swift Argument Parser for command-line tools.
competition-details
Exclude competition details from agent work.
swift-observable
Migration guide for updating SwiftUI apps from ObservableObject to the @Observable macro.
update-docs
You will generate LLM-optimized documentation with concrete file references and flexible formatting.
mcp-best-practices
Best practices for developing Model Context Protocol (MCP) tools with proper configuration and behavior.