cursor-context

A Cursor rule that points developers to the repository's canonical engineering rules in context/rules/ instead of copying them into another file.

In plain words
What is it for?
It is for making Cursor follow the shared project rules and helping generated agent configurations reference the same source.
Why use it?
It reduces the risk of conflicting or outdated instructions when several tools use the same codebase.

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/vexloca/ctxinit/cursor-context
Clone the repo
git clone --depth 1 https://github.com/VexloCa/ctxinit
Per session 117 This file is loaded in full into every session.
When invoked 117 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.00117 $0.00117
Opus 5 $0.00059 $0.00059
Sonnet 5 $0.00023 $0.00023
Haiku 4.5 $0.00012 $0.00012

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

Security

Grade A, and why

cursor-context 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.

templates/agents/cursor-context.mdc · 11 lines

What it actually says

All binding rules for this repo live in context/rules/00…06 — read and follow them; start at context/README.md for orientation. This stub exists only because Cursor needs a file to glob. Do not add rule text here — context/rules/ is the single canonical copy, and any agent generating its own config must likewise point to context/ rather than copy from it.

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 · 11 lines · 117 tokens per session scan A 793a9a22bda6

Subscribe to this mod's changes

cursor-context is a cursor rule published in the GitHub repository VexloCa/ctxinit (2 stars, last pushed 1mo ago), licensed MIT. It adds 117 tokens to every session, about $0.0006 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.