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.
npx agentmods add rules/opensquad-ai/opensquad/desktop-release-gategit clone --depth 1 https://github.com/opensquad-ai/opensquadWhat 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.00609 |
| Opus 5 | $0.00000 | $0.00304 |
| Sonnet 5 | $0.00000 | $0.00122 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade A, and why
desktop-release-gate 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.
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.
Desktop release gate (local first)
When fixing or changing the packaged OpenSquad desktop app (Electron, PyInstaller backend, tray/icons, startup, auto-update):
Required before push / tag / build-desktop CI
- Unit/smoke tests — run the ci-fast subset (
ruff, targetedpytest,npm run build). - Local backend build + frozen smokes (Windows; ~5 min + ~30 s):
This catches import-time writes and workspace path bugs without waiting for Electron/Setup.scripts\build_backend.bat uv run python scripts\smoke_frozen_all.py - Full packaged build when changing Electron/UI/installer (optional for backend-only fixes):
cd src\opensquad\gateway\nexuschat-pro npm ci npm run electron:win - Manual smoke test of the produced installer or portable exe (when shipping UI/installer changes):
- App window shows UI (not blank / not stuck on “Starting…”)
- Tray icon visible
- No “Backend did not start in time” dialog
- Only then: commit → merge
main→ push tag or triggerbuild-desktop.yml.
Do not push a release tag or ask the user to install from CI as the first verification step for desktop startup/UI bugs.
Windows local build (mirrors CI)
From repo root:
pip install -e .
pip install pyinstaller pillow playwright
playwright install chromium
scripts\build_backend.bat
cd src\opensquad\gateway\nexuschat-pro
npm ci
npm run electron:win
Installers land in build/release/ (e.g. OpenSquad-*-win-x64-Setup.exe or
*-Portable.exe). Run one and confirm the above smoke checks.
Faster iteration (code-only, not a release gate)
npm run build && node scripts/compile-electron.mjs— compile frontend + main processnpm run electron:dev:fast— needs pre-built backend inresources/orbuild/backend-win/
Use full electron:win before any release/tag push.
CI after local pass
- New release: merge to
main, tagvX.Y.Z, push tag (triggers Release + Build Desktop App). - Refresh existing release assets:
gh workflow run build-desktop.yml --ref main -f release_tag=vX.Y.Z
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.
- 2d ago First seen · 66 lines · 0 tokens per session scan A a9478240791c
desktop-release-gate is a cursor rule published in the GitHub repository opensquad-ai/opensquad (5 stars, last pushed 19d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 609 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.
Other cursor rules, from other repositories
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.
cli-error-handling
CLI command error handling patterns.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.