monorepo

A configuration rule for a monorepo, which is one repository containing multiple related projects or packages. The provided text describes it only as a test rule.

In plain words
What is it for?
Use it to represent a test rule for monorepo configuration.
Why use it?
It can provide a shared place for monorepo-specific guidance, although this example does not define any actual behavior.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/fireharp/cursor-rules/monorepo
Clone the repo
git clone --depth 1 https://github.com/fireharp/cursor-rules
Per session 35 This file is loaded in full into every session.
When invoked 35 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00035 $0.00035
Opus 5 $0.00017 $0.00017
Sonnet 5 $0.00007 $0.00007
Haiku 4.5 $0.00003 $0.00003

Measured 2d ago against content hash cd93d98fec6a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

test-rules/monorepo.mdc · 6 lines

What it actually says

Monorepo Rule

This is a test rule for monorepo setup.

Rule Name: monorepo Description: A test rule for monorepo configuration

Changes

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.

  1. 2d ago First seen · 6 lines · 35 tokens per session scan A cd93d98fec6a

Subscribe to this mod's changes

monorepo is a cursor rule published in the GitHub repository fireharp/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It adds 35 tokens to every session, about $0.0002 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-31.