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.
git clone --depth 1 https://github.com/platinoff/poolAIWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/platinoff/poolai/cursorrules)<a href="https://agentmods.dev/rules/platinoff/poolai/cursorrules"><img src="https://agentmods.dev/badge/rules/platinoff/poolai/cursorrules/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/platinoff/poolai/cursorrules"><img src="https://agentmods.dev/badge/rules/platinoff/poolai/cursorrules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00790 | $0.00790 |
| Opus 5.5 | $0.00316 | $0.00316 |
| Sonnet 5.5 | $0.00158 | $0.00158 |
| Haiku 4.5 | $0.00079 | $0.00079 |
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 1mo 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.
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 localcargo/git/scripts — no PowerShell, no cmd (seerust-architect.mdc,msys2-windows.mdc). - Patches:
rust-toolchain.toml,.cursor,.vscode,scripts/
Runtime stack
runtime-stack-policy.mdc— alwaysApply: Rust primary; zero.pyin repo; JS UI;poolai-openapi-gap-auditbin.
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 rulesgit-workflow.mdc- Git workflow, commit format, and push order rulesmsys2-windows.mdc- MSYS2 and Windows development environment rules (bash, NOT PowerShell)scripts.mdc- Scripts structure and file listing rulesproject-structure.mdc- Project organization and file naming rulesrust.mdc- Rust coding standards and patternsai-assistant.mdc- AI assistant rules and key document referencesautonomous-orchestrator.mdc- Автономна розробка: оркестратор, субагенти, AUTO_RUNfunctionality-management.mdc- Менеджер функціоналу: FM-*, охоплення docs, §5.1
Quick Reference
For detailed rules, see the corresponding file in .cursor/rules/:
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.
- 1mo ago First seen · 55 lines · 790 tokens per session scan A 0fbe60f8fb2c
cursorrules is a cursor rule published in the GitHub repository platinoff/poolAI (4 stars, last pushed yesterday), licensed MIT. It adds 790 tokens to every session, about $0.0032 per session on Opus 5.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.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.