three-repo-load-gate

A rule for testing three repositories when the one-minute system load average is below 20. A repository is a project's source-code directory, and load average indicates how much work a computer is handling.

In plain words
What is it for?
Use it to decide when to run the formal three-repository cold-start tests and isolated quality checks, while recording load without rejecting the run when load is 20 or higher.
Why use it?
It prevents high load from being used as a reason to skip the required test matrix; only available memory of at least 4 GiB is a hard stop.

Cursor rule for Cursor

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/lkyprogramer/codex-java-lsp-mcp/three-repo-load-gate
Clone the repo
git clone --depth 1 https://github.com/lkyprogramer/codex-java-lsp-mcp

Made for: Cursor.

Per session 216 This file is loaded in full into every session.
When invoked 216 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.00216 $0.00216
Opus 5 $0.00108 $0.00108
Sonnet 5 $0.00043 $0.00043
Haiku 4.5 $0.00022 $0.00022

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

Security

Grade A, and why

three-repo-load-gate 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.

.cursor/rules/three-repo-load-gate.mdc · 14 lines

What it actually says

三仓 load 政策

1 分钟 load average 小于 20 时,必须执行正式三仓 cold-nolsp 矩阵与隔离质量复测。不要因为主机“不够安静”、per-CPU 0.7、或历史 HANDOFF 里的 0.7x 经验阈值而跳过、推迟或改成小样本。

  • 真源:docs/phase-v4/three-repo-host-load-policy.md
  • 常量:scripts/host-quiet.mjsTHREE_REPO_LOADAVG_PROCEED_BELOW = 20
  • load 永远不是三仓矩阵的拒绝门;load >= 20 只记录,不 throw
  • 唯一主机硬门:可用内存 ≥ 4 GiB
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. yesterday First seen · 14 lines · 216 tokens per session scan A e1d787fa82f7

Subscribe to this mod's changes

three-repo-load-gate is a cursor rule published in the GitHub repository lkyprogramer/codex-java-lsp-mcp (1 stars, last pushed 8d ago), licensed Apache-2.0. It adds 216 tokens to every session, about $0.0011 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.