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/boundaries)<a href="https://agentmods.dev/rules/louisbrulenaudet/monorepo-template/boundaries"><img src="https://agentmods.dev/badge/rules/louisbrulenaudet/monorepo-template/boundaries.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.1 | $0.00415 | $0.00415 |
| Opus 5 | $0.00208 | $0.00208 |
| Sonnet 5 | $0.00083 | $0.00083 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
boundaries 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 8d 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
Package Boundaries
turbo.json under boundaries.tags is the source of truth and it is already commented - read it rather than trusting a copy. pnpm boundaries (inside pnpm run ci) enforces it: a violation fails CI, it is not a convention. This file carries only what the config cannot say about itself.
Tag map
| Tag | Packages |
|---|---|
app |
every front-* / worker-* / queue-* / webhook-* / mcp-* |
contracts |
@repo/dtos-common |
contracts-base |
@repo/enums-common |
lib |
@repo/correlation-id |
config |
@repo/typescript-config, @repo/vitest-config |
Invariants
- Nothing may depend on an
app.app.dependents.denylists all four tags, so apps are entry points and never installable dependencies. Worker-to-Worker calls go through service-binding RPC declared inwrangler.jsonc- never a package import. - The contract chain cannot invert.
contracts→contracts-base→configare declared as allow-lists, so the documentedenums → dtosdirection is genuinely enforced and cannot become a cycle. - A new package must declare its tag. Add
turbo.jsonwith"extends": ["//"]and atagsentry, orpnpm boundariesreports it as untagged. configdepends on nothing internal.config.dependencies.allowis[], so@repo/typescript-configand@repo/vitest-configcannot depend on any tagged workspace package.
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.
- 8d ago First seen · 27 lines · 415 tokens per session scan A 6f66ae265a3b
boundaries is a cursor rule published in the GitHub repository louisbrulenaudet/monorepo-template (19 stars, last pushed 7d ago), licensed Apache-2.0. It adds 415 tokens to every session, about $0.0021 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
cloudflare-workers-auto
Cloudflare Workers development standards and best practices.
cloudflare-workers-hono-auto
Cloudflare Workers with Hono framework development standards and best practices.
laravel-php-auto
Laravel and PHP Development Standards.
mcp-server
This rule explains how to create a remote MCP server on Cloudflare with both free and paid tools (using Stripe).
api-endpoint-template
Template for creating new FastAPI endpoints.
api-integration
Frontend API Integration Patterns.