LeanCTX is a local Rust program that controls the repository context an AI coding agent receives, including selecting, compressing, remembering, and tracking information. Developers use it alongside coding agents to reduce repeated context and manage what those agents read and execute, while the catalogue entries provide related rules, skills, and instructions.
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/yvgude/lean-ctxWrote 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/yvgude/lean-ctx/leanctx-ip-governance)<a href="https://agentmods.dev/rules/yvgude/lean-ctx/leanctx-ip-governance"><img src="https://agentmods.dev/badge/rules/yvgude/lean-ctx/leanctx-ip-governance/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/yvgude/lean-ctx/leanctx-ip-governance"><img src="https://agentmods.dev/badge/rules/yvgude/lean-ctx/leanctx-ip-governance.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.00174 | $0.00174 |
| Opus 5.5 | $0.00070 | $0.00070 |
| Sonnet 5.5 | $0.00035 | $0.00035 |
| Haiku 4.5 | $0.00017 | $0.00017 |
Grade A, and why
leanctx-ip-governance 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.
What it actually says
Before editing, read .agents/skills/leanctx-ip-governance/SKILL.md and AGENTS.md, including references/PRODUCT_SCOPE.md and references/CONNECTOR_AND_DECISION_SECURITY.md. LeanCTX is Context Gateway (Select → Control → Prove); new work must map authorized source→decision→bundle/receipt. General agent/model orchestration is not product scope; team coordination context (presence, leases, workspace bus, shared work graph) is. Preserve existing Apache rights, do not auto-delete OSS, keep new EE private, no public publish without real founder+independent release approval. State source ACL, integration coverage, affected licence, tests and rollback.
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.
- 2d ago First seen · 7 lines · 174 tokens per session scan A 599a94b912e5
leanctx-ip-governance is a cursor rule published in the GitHub repository yvgude/lean-ctx (3,917 stars, last pushed yesterday), licensed Apache-2.0. It adds 174 tokens to every session, about $0.0007 per session on Opus 5.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-10-30.
Other cursor rules, from other repositories
cdv
How to drive the cdv MCP sidecar (observe, verify, remember, resume).
roslyn-mcp-overview
RoslynMcpServer — architecture, layout, version, DI.
roslyn-mcp-pitfalls
Known pitfalls and regression lessons from production use.
roslyn-mcp-docs-agents
Docs sync AGENTS/README, agent conventions, PowerShell, secrets.
roslyn-mcp-version-bump
Auto-bump Version after successful MCP self-build and reload.
roslyn-mcp-decompile
Assembly resolve, ILSpy decompile, NuGet/BCL fallback.