msys2-windows

A set of development rules for building PoolAI on Windows with MSYS2, a Unix-like environment that provides Bash and GNU development tools.

In plain words
What is it for?
It helps configure and verify Rust development, Git, scripts, GNU linking, long-path handling, and troubleshooting for files in the build directory.
Why use it?
It clarifies which terminal, compiler, Rust toolchain, paths, and Windows settings the project expects, reducing environment-related build failures.

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/msys2-windows
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 1,068 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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01068
Opus 5 $0.00000 $0.00534
Sonnet 5 $0.00000 $0.00214
Haiku 4.5 $0.00000 $0.00107

Measured 2d ago against content hash 9f33389cec34, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

msys2-windows 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 2d 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.

.cursor/rules/msys2-windows.mdc · 66 lines

How it starts

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

MSYS2 & Windows Development Environment

⚠️ CRITICAL: MSYS2 bash only — no PowerShell, no cmd

Terminal: C:\msys64\usr\bin\bash.exe (MSYS2 UCRT64) for all dev work: cargo, git, scripts, and any verification you run locally.
CI on GitHub uses its own runner environment; locally, stay in MSYS2 bash (see rust-architect.mdc, git-push.md).

Windows 11 (24H2+ / builds 26100+; e.g. 26200)

  • Windows Defender can slow or lock files under target/ — optional exclusion for the repo target folder (or whole repo) if builds/tests stall.
  • Long paths: if cargo reports path length issues, enable long paths in Windows or keep the repo on a shorter path (e.g. S:\rust\poolAI is fine).
  • rust-toolchain.toml pins x86_64-pc-windows-gnu; the active host may still be MSVC (rustc -vVhost: …-msvc). For GNU linking you need MSYS2 gcc/x86_64-w64-mingw32-gcc on PATH (see .cargo/config.toml). If the host is MSVC-only, align with rustup override / installed toolchains.

Project patches (конфіг)

  • rust-toolchain.toml — Rust 1.92.0, x86_64-pc-windows-gnu, rustfmt, clippy
  • .cursor — Cursor rules, commands, hooks.json (rules/, commands/); без .ps1
  • .vscode — Terminal profile "bash (MSYS2)", Rust Analyzer
  • scripts/ — Bash scripts only (.sh). Run via MSYS2 bash.

Terminal setup

  • Profile: "bash (MSYS2)" in .vscode/settings.json
  • Path: C:\msys64\usr\bin\bash.exe with -l
  • Env: MSYSTEM=UCRT64, CHERE_INVOKING=1
  • PATH: C:\msys64\ucrt64\bin;C:\msys64\usr\bin (and cargo)

Always use MSYS2 bash for

  • All cargo commands (check, build, test, fmt, clippy)
  • All git operations (copy-paste block in .cursor/commands/git-push.md; no .sh wrappers for git)
  • Running scripts/*.sh when needed

Tooling Checks (rustc/cargo/clippy/cl)

  • Version sanity (run once per session if something fails):
    • rustc --version
    • cargo --version
    • cargo clippy --version
  • MSRV note (cloud-sdk/AWS SDK): cloud_mock_integration requires rustc >= 1.88. If your rustc --version is lower (e.g. 1.87.0), install rustup+the toolchain from rust-toolchain.toml or upgrade the MSYS2 Rust package before running cloud tests.
  • MSVC cl.exe note:
    • Default toolchain is GNU (x86_64-pc-windows-gnu); cl.exe is usually not needed.
    • If you switch to an MSVC host/toolchain, use a Visual Studio / MSVC environment where cl is on PATH, then run cargo from that same environment (still avoid ad-hoc PowerShell/cmd-only workflows for this repo).

Read the full file on GitHub · 66 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. 2d ago First seen · 66 lines · 0 tokens per session scan A 9f33389cec34

Subscribe to this mod's changes

msys2-windows 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 1,068 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.