cursorrules

A compatibility file for Cursor editor rules. The active rules are stored as `.mdc` files in the `.cursor/rules/` directory.

In plain words
What is it for?
Guiding Cursor sessions on project context, terminal choice, patch locations, Rust-only runtime rules, and related project workflows.
Why use it?
It points existing users to the current rule location and preserves older references to the former rules file.

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

Made for: Cursor.

Per session 790 This file is loaded in full into every session.
When invoked 790 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.00790 $0.00790
Opus 5 $0.00395 $0.00395
Sonnet 5 $0.00158 $0.00158
Haiku 4.5 $0.00079 $0.00079

Measured yesterday against content hash 0fbe60f8fb2c, 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.

.cursor/rules/.cursorrules · 55 lines

How it starts

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

Cursor Rules for PoolAI Project

⚠️ IMPORTANT: This file is maintained for backward compatibility.
All rules are now in .cursor/rules/ directory as .mdc files.

Chat / подальша робота з чатом

При старті сесії або запиті «налаштуйся для роботи з чатом» — читай chat-context.mdc першим. Там: проект, ключові документи, термінал (MSYS2 only), git (без .sh), патчі, поточний стан і далі.

Terminal & patches

  • Terminal: C:\msys64\usr\bin\bash.exe (MSYS2 UCRT64) for all local cargo/git/scripts — no PowerShell, no cmd (see rust-architect.mdc, msys2-windows.mdc).
  • Patches: rust-toolchain.toml, .cursor, .vscode, scripts/

Runtime stack

  • runtime-stack-policy.mdcalwaysApply: Rust primary; zero .py in repo; JS UI; poolai-openapi-gap-audit bin.

Rules Location

All project rules are organized in .cursor/rules/:

  • poolai-agent-roles.mdc - 👥 VDT ролі + субагенти + §5.1/§5.12 (always on)
  • runtime-stack-policy.mdc - ⛔ Rust-only runtime; block Python proposals (always on)
  • chat-context.mdc - 🧭 Стартовий контекст чату (при «налаштуйся» / подальша робота)
  • rust-architect.mdc - ⭐ Rust Architect workflow and concept file usage (READ FIRST)
  • documentation.mdc - Documentation structure and file organization rules
  • git-workflow.mdc - Git workflow, commit format, and push order rules
  • msys2-windows.mdc - MSYS2 and Windows development environment rules (bash, NOT PowerShell)
  • scripts.mdc - Scripts structure and file listing rules
  • project-structure.mdc - Project organization and file naming rules
  • rust.mdc - Rust coding standards and patterns
  • ai-assistant.mdc - AI assistant rules and key document references
  • autonomous-orchestrator.mdc - Автономна розробка: оркестратор, субагенти, AUTO_RUN
  • functionality-management.mdc - Менеджер функціоналу: FM-*, охоплення docs, §5.1

Quick Reference

For detailed rules, see the corresponding file in .cursor/rules/:

Read the full file on GitHub · 55 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. yesterday First seen · 55 lines · 790 tokens per session scan A 0fbe60f8fb2c

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository platinoff/poolAI (4 stars, last pushed 8d ago), licensed MIT. It adds 790 tokens to every session, about $0.0040 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.