cursor-environment-baseline

A set of rules for checking the local Cursor editor, Rust, Cargo, and Git setup before changing automation files.

In plain words
What is it for?
Checking installed tool versions and keeping Cursor commands, hooks, and rules aligned with the current development environment.
Why use it?
It helps prevent automation changes from relying on outdated software versions or incorrect Windows and MSYS2 paths.

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/platinoff/poolai/cursor-environment-baseline
Clone the repo
git clone --depth 1 https://github.com/platinoff/poolAI

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,460 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.01460
Opus 5 $0.00000 $0.00730
Sonnet 5 $0.00000 $0.00292
Haiku 4.5 $0.00000 $0.00146

Measured 2d ago against content hash 9a4340feb15b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cursor-environment-baseline 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.

.cursor/rules/cursor-environment-baseline.mdc · 60 lines

How it starts

The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Cursor Environment Baseline

  • Keep Cursor workflows aligned with the installed local stack before making automation changes.
  • Baseline for this machine (verified 2026-07-27):
    • cursor: 3.13.21 (C:\Program Files\cursor\resources\app\bin\cursor.cmd — not in MSYS2 PATH; confirm via resources/app/package.json version)
    • rustc: 1.92.0 (rustup stable-x86_64-pc-windows-gnu; ignore MSYS2 pacman 1.87 if present)
    • cargo: 1.92.0
    • git: 2.50.0 (MSYS2 UCRT64)

Update-aware checks

  • When updating .cursor/commands/, .cursor/hooks.json, or .cursor/rules/, validate current CLI output first.
  • Re-check tool versions after OS/package updates using:
    • Cursor: package.json under C:\Program Files\cursor\resources\app\ (or cursor.cmd --version outside MSYS2)
    • rustc --version (with RUSTUP_TOOLCHAIN=stable-x86_64-pc-windows-gnu)
    • cargo --version
    • git --version

Cursor release alignment (latest known)

  • Local desktop build: 3.13.21 (2026-07-27). Patch after 3.13.10 — Windows Agents Changes-tab / switch-agent chat / subagent back-nav fixes expected on 3.13 line; not a new numbered public feature write-up (changelog still tops at 3.11 + Jul 22 Router).
  • Public changelog: latest numbered IDE release is 3.11 (Jul 10, 2026): side chats (/side, /btw), Agents Window transcript search (Cmd/Ctrl+K), cloud conversation hooks. Jul 17 = Slack-only. Jul 22 = Cursor Router (Auto Cost/Balance/Intelligence).
  • Post-update research: docs/development/CURSOR_UPDATE_RESEARCH_2026-07-27.md · previous …2026-07-24.md.

Automatic execution (Run Modes)

  • Settings → Agents → Approvals & Execution. Prefer Auto-review for PoolAI drain / абракадабра (not Run Everything).
  • Project steer: .cursor/permissions.json — allow MSYS2/cargo/git/vision-sync drain; block force-push, secrets, history rewrite, Python product files.
  • sandbox.json: optional; Seatbelt/Landlock documented for macOS/Linux. Windows VDT (MSYS2) often runs unsandboxed via classifier — do not add project sandbox.json without OWNER.
  • Legacy YOLO / Auto-Run naming → Run Modes (3.6+). Write Auto-review in rules, not YOLO.
  • Cloud Agents do not use Run Modes.
  • Chat Mode (Agent/Plan via Shift+Tab) is separate from Run Mode.
  • Cursor Router (Auto): for long абракадабра drain prefer Balance or Intelligence (not Cost).

Read the full file on GitHub · 60 lines

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 · 60 lines · 0 tokens per session scan A 9a4340feb15b

Subscribe to this mod's changes

cursor-environment-baseline is a cursor rule published in the GitHub repository platinoff/poolAI (4 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,460 tokens. 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.