cursorrules

A set of coding rules for using lean-ctx, a context tool that reads, searches, and maps project files in compact form. It tells the agent which tool to prefer for common tasks.

In plain words
What is it for?
Use it when reading files, searching code, viewing directory layouts, running shell commands, or making search-and-replace edits. It is intended for repositories where keeping AI context small matters.
Why use it?
It helps reduce the amount of project text placed into the AI's working context, which can save tokens. It also gives a fallback for editing when the usual file-reading tool is unavailable.

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/davidruzicka/mcp4openapi/cursorrules
Clone the repo
git clone --depth 1 https://github.com/davidruzicka/mcp4openapi

Made for: Cursor.

Per session 183 This file is loaded in full into every session.
When invoked 183 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.00183 $0.00183
Opus 5 $0.00092 $0.00092
Sonnet 5 $0.00037 $0.00037
Haiku 4.5 $0.00018 $0.00018

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

Security

Grade A, and why

cursorrules 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.

.cursorrules · 15 lines

What it actually says

lean-ctx — Context Engineering Layer

PREFER lean-ctx MCP tools over native equivalents for token savings:

PREFER OVER Why
ctx_read(path) Read Cached, 8 compression modes
ctx_shell(command) Shell Pattern compression
ctx_search(pattern, path) Grep Compact results
ctx_tree(path, depth) ls / find Directory maps
ctx_edit(path, old_string, new_string) Edit (when Read unavailable) Search-and-replace without native Read

Edit files: use native Edit/StrReplace if available. If Edit requires Read and Read is unavailable, use ctx_edit. Write, Delete, Glob — use normally. NEVER loop on Edit failures — switch to ctx_edit immediately.

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 · 15 lines · 183 tokens per session scan A 18788da53813

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository davidruzicka/mcp4openapi (0 stars, last pushed 14d ago), licensed MIT. It adds 183 tokens to every session, about $0.0009 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.