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/documentation)<a href="https://agentmods.dev/rules/platinoff/poolai/documentation"><img src="https://agentmods.dev/badge/rules/platinoff/poolai/documentation/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/documentation"><img src="https://agentmods.dev/badge/rules/platinoff/poolai/documentation.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.01660 | $0.01660 |
| Opus 5.5 | $0.00664 | $0.00664 |
| Sonnet 5.5 | $0.00332 | $0.00332 |
| Haiku 4.5 | $0.00166 | $0.00166 |
Grade A, and why
documentation 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Structure Rules
Canonical documentation order (PoolAI)
Узгоджено з кореневим README.md (Documentation map): кроки 1–12. Останні кроки:
- 11.
docs/catalog/FUNCTIONALITY_DIGEST_2026-04-06.md— структурований витяг функціоналу (модулі, features, HTTP-шари). Оновлювати після значних змін уsrc/або публічному API. - 12.
docs/catalog/FUNCTION_MANAGEMENT.md— керування функціоналом: звірка зі сталевим станом, прогалини, чернетки тікетів (FM-*), посилання на плани та концепти. Правило агента:.cursor/rules/functionality-management.mdc.
Каталог docs/catalog/ призначений для зведень і індексів, які не є «планом розробки» (docs/development/) і не «статусом» (docs/status/).
Project skill: .agents/skills/poolai-documentation/SKILL.md (mirrors: .cursor/skills/, .opencode/skills/) — стислі інструкції для агента з цього порядку та витягу.
Runtime stack: .cursor/rules/runtime-stack-policy.mdc — Rust primary; Python заборонено в продукті (архівні docs не канон).
Авторозробка: найновіший docs/development/AUTO_RUN_SESSION_*.md, реєстр патернів docs/development/AUTO_DEV_PATTERNS.md, правила .cursor/rules/autonomous-orchestrator.mdc та .cursor/rules/functionality-management.mdc.
📁 Documentation Structure - STRICT RULES
Human-readable taxonomy (Ukrainian): docs/STRUCTURE.md — canonical entry points, folder meanings, legacy flat files under docs/, Cursor rules, inventory.
⚠️ CRITICAL: All documentation MUST be in docs/ directory
NEVER create .md files in the root directory (except README.md and README.uk.md)
File Organization:
- All documentation →
docs/directory - All Cursor rules →
.cursor/rules/directory - Dev/ops launchers →
bin/; toolchain/deploy →scripts/; Rust CLIs →src/bin/(seedocs/development/REPOSITORY_LAYOUT.md) - Troubleshooting guides →
docs/troubleshooting/
Directory Structure
When creating or referencing documentation, use this structure:
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 · 147 lines · 1,660 tokens per session scan A 7175859c217f
documentation is a cursor rule published in the GitHub repository platinoff/poolAI (4 stars, last pushed yesterday), licensed MIT. It adds 1,660 tokens to every session, about $0.0066 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.