cursorrules

Operating rules for an agent that require reading the project's local instructions before handling each request and keeping responses short.

In plain words
What is it for?
Use them as a general session rule when working in projects that define instructions in their .agents/skills directory.
Why use it?
They help ensure work follows the project's constraints and avoids wasting context on unnecessary detail.

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

Made for: Cursor.

Per session 41 This file is loaded in full into every session.
When invoked 41 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.00041 $0.00041
Opus 5 $0.00020 $0.00020
Sonnet 5 $0.00008 $0.00008
Haiku 4.5 $0.00004 $0.00004

Measured 2d ago against content hash c97bb564e851, 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 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.

.cursorrules · 2 lines

What it actually says

Before processing any user prompt, always read and strictly adhere to the operational constraints, context caching rules, and module boundaries defined in .agents/skills. Keep responses compact and direct to preserve context window longevity.

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 · 2 lines · 41 tokens per session scan A c97bb564e851

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository nebius/nebius-physical-ai (22 stars, last pushed 2d ago), licensed Apache-2.0. It adds 41 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-30.