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/opensquad-ai/opensquadWrote 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/opensquad-ai/opensquad/desktop-release-gate)<a href="https://agentmods.dev/rules/opensquad-ai/opensquad/desktop-release-gate"><img src="https://agentmods.dev/badge/rules/opensquad-ai/opensquad/desktop-release-gate/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/opensquad-ai/opensquad/desktop-release-gate"><img src="https://agentmods.dev/badge/rules/opensquad-ai/opensquad/desktop-release-gate.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.00000 | $0.00770 |
| Opus 5.5 | $0.00000 | $0.00308 |
| Sonnet 5.5 | $0.00000 | $0.00154 |
| Haiku 4.5 | $0.00000 | $0.00077 |
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 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 — 71 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, nestedscripts\build_backend.bat uv run python scripts\check_backend_bundle.py uv run python scripts\smoke_frozen_all.pyopensquad/buildpollution, and workspace path bugs without waiting for Electron/Setup. - Full packaged build when changing Electron/UI/installer (preferred one-shot):
Or backend-only then Electron:powershell -ExecutionPolicy Bypass -File scripts\build_desktop.ps1scripts\build_backend.bat 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:
uv sync --python 3.11
powershell -ExecutionPolicy Bypass -File scripts\build_desktop.ps1
Installers land in build/release/ (e.g. OpenSquad-*-win-x64-Setup.exe or
*-Portable.exe). Run one and confirm the above smoke checks.
Never place Electron/release* trees under src/opensquad/build/ — PyInstaller
collect_data_files("opensquad") used to nest them into run.exe (~400MB+).
Official output is always repo-root build/release/.
Faster iteration (code-only, not a release gate)
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 Changed · +5 lines 0f402ad371d2
- 1mo 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 (7 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 770 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
08-github-workflow-standards
GitHub issue/PR/milestone standards for Matryca Plumber (OSS maintainer rigor).
06-auto-changelog
Always keep the CHANGELOG updated with meaningful changes.
05-release-preparation
Prepare a semver release (CHANGELOG, pyproject.toml, uv.lock, checks).
release
PULSE Release Process - Checklist for publishing updates.
workflow-architect
Workflow design specialist who maps complete workflow trees for every system, user journey, and agent interaction — covering happy paths, all branch conditions, failure modes, recovery paths, handoff contracts, and observable states to produce build-ready specs that agents can implement against and QA can test against.
playwright-api-testing
You are an expert QA engineer with deep knowledge of Playwright and TypeScript, tasked with creating API tests for web applications.