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/scripts)<a href="https://agentmods.dev/rules/platinoff/poolai/scripts"><img src="https://agentmods.dev/badge/rules/platinoff/poolai/scripts/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/scripts"><img src="https://agentmods.dev/badge/rules/platinoff/poolai/scripts.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.00931 | $0.00931 |
| Opus 5.5 | $0.00372 | $0.00372 |
| Sonnet 5.5 | $0.00186 | $0.00186 |
| Haiku 4.5 | $0.00093 | $0.00093 |
Grade A, and why
scripts 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scripts Structure Rules
🔧 Scripts Structure - STRICT RULES
⚠️ CRITICAL: Bash only — No PowerShell, No cmd
- All dev/git in MSYS2 bash (
C:\msys64\usr\bin\bash.exe). Scripts:scripts/*.shonly. - NEVER create
.shor.ps1in project root.
Scripts Directory Structure
scripts/
├── README.md # Scripts documentation
├── check_target_disk.sh # Free space + target/ size guard (before heavy cargo)
├── fix_cargo_now.sh # Cargo fix script
├── fix_gcc.sh # GCC fix script
├── install_gcc.sh # GCC installation
├── setup_rust_path.sh # Rust PATH setup
├── QUICK_FIX_RUST_PATH.sh # Quick Rust PATH fix
├── verify_build.sh # Build verification
└── PUSH_COMMANDS.sh # Git push helper
(Приклад; у каталозі можуть бути й інші .sh. Нові .ps1 не додавати.)
Rules for Creating New Scripts
-
Always create in
scripts/directory:- Build scripts →
scripts/ - Setup scripts →
scripts/ - Utility scripts →
scripts/ - CI/CD scripts →
scripts/(orscripts/ci/for multiple) - Bash scripts (
.sh) →scripts/only. Do not add.ps1.
- Build scripts →
-
File naming:
- Use lowercase with underscores:
setup_rust_path.sh - Use descriptive names:
fix_cargo_now.sh - Use UPPERCASE for important scripts:
PUSH_COMMANDS.sh(optional) - No
.ps1in this repo’s workflow (use bash / MSYS2).
- Use lowercase with underscores:
-
When user asks to create a script:
- Always create in
scripts/ - Add description in
scripts/README.md - Make executable:
chmod +x scripts/script_name.sh(for.shfiles)
- Always create in
Script References
- In documentation:
scripts/script_name.sh - In Rust code comments:
scripts/script_name.sh - In CI/CD configs:
scripts/script_name.sh - When listing files: Use descriptive names, NOT
.ps1or.psextensions in lists
⚠️ File Listing Rules
When creating file lists or inventories:
- ❌ NEVER use
.ps1or.psextensions in file lists - ❌ NEVER use PowerShell-specific syntax in documentation lists
- ✅ Use descriptive names:
setup_msvc_environment.ps1→ "MSVC environment setup script" - ✅ Group by category: "Bash scripts" (preferred)
- ✅ Use markdown lists or tables, not PowerShell command output
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 · 94 lines · 931 tokens per session scan A ce71f48f32e7
scripts is a cursor rule published in the GitHub repository platinoff/poolAI (4 stars, last pushed yesterday), licensed MIT. It adds 931 tokens to every session, about $0.0037 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.