Project rules for organizing scripts as Bash files inside a scripts/ directory, with development and Git commands run through MSYS2 bash.

They are for deciding where build, setup, utility, and CI scripts belong and how they should be named and run.

They prevent scripts from being scattered around the project and exclude unsupported PowerShell scripts.

scripts — Cursor rule by platinoff

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/scripts

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 931 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00931
Opus 5	$0.00000	$0.00465
Sonnet 5	$0.00000	$0.00186
Haiku 4.5	$0.00000	$0.00093

Measured yesterday against content hash ce71f48f32e7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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/scripts.mdc · 94 lines

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/*.sh only.
NEVER create .sh or .ps1 in 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/ (or scripts/ci/ for multiple)
- Bash scripts (.sh) → scripts/ only. Do not add .ps1.
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 .ps1 in this repo’s workflow (use bash / MSYS2).
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 .sh files)

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 .ps1 or .ps extensions in lists

⚠️ File Listing Rules

When creating file lists or inventories:

❌ NEVER use .ps1 or .ps extensions 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

Read the full file on GitHub · 94 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.

yesterday First seen · 94 lines · 931 tokens per session scan A ce71f48f32e7

Subscribe to this mod's changes

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

DevOps and cloud Git and workflow

scripts

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Scripts Structure Rules

🔧 Scripts Structure - STRICT RULES

⚠️ CRITICAL: Bash only — No PowerShell, No cmd

Scripts Directory Structure

Rules for Creating New Scripts

Script References

⚠️ File Listing Rules

What this file has done since we first saw it

Other cursor rules, from other repositories

angular-20

dev-standard

typescript

coolify-ai-docs

python_lib

specs