cursorrules

A set of instructions for AI coding agents working on setmac, a macOS development-environment installer with a SwiftUI app and a Python command-line tool. It defines commit names, release rules, required commands, and project constraints.

In plain words
What is it for?
Use it when changing setmac code, preparing commits or releases, choosing the correct command runner, or working with its command-line and GUI components.
Why use it?
It keeps automated changes consistent with the project's versioning, release, and tooling policies.

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/v0id-user/setmac/cursorrules
Clone the repo
git clone --depth 1 https://github.com/v0id-user/setmac

Made for: Cursor.

Per session 565 This file is loaded in full into every session.
When invoked 565 The same file — it is already loaded in full.
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.00565 $0.00565
Opus 5 $0.00282 $0.00282
Sonnet 5 $0.00113 $0.00113
Haiku 4.5 $0.00056 $0.00056

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

Security

Grade A, and why

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

.cursorrules · 47 lines

How it starts

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

setmac — AI Rules

What This Project Is

macOS dev environment installer. SwiftUI app + Python CLI, shared tools.json manifest.

Commit Convention

Use Conventional Commits for versioning and changelogs:

feat: add new feature
fix: resolve bug
chore: maintenance
docs: documentation
style: formatting
test: tests
ci: CI changes

Types: feat, fix, refactor, chore, docs, style, test, ci. Use feat!: or fix!: for breaking changes.

Split commits: One logical change per commit. Group related edits (e.g. all release pipeline files in one feat, all doc updates in one docs).

Release Policy

  • Default channel: canary or beta (prerelease-first). Push to canary or beta for automatic prereleases.
  • Stable: Only when user explicitly says "release stable" or "promote to stable". Never trigger stable releases by default.
  • Version bumping: Never manually edit version in pyproject.toml, justfile, bundle.sh, or init.py. semantic-release owns versioning.

Must Follow

  • CLI binary is setmac-cli not setmac (case-insensitive APFS collision with GUI binary Setmac)
  • Use just (justfile) not make as command runner
  • No Xcode IDE. SPM + CLI only (swift build, swift run)
  • No hardcoded tool names — everything from tools.json
  • Window not WindowGroup (single-window app)
  • macOS 26+ (Tahoe), Liquid Glass UI
  • Python CLI managed with uv, entry point setmac
  • JSON-line protocol on stdout, thread-safe with threading.Lock()
  • os.Logger subsystem: com.v0id.setmac
  • CLIBridge uses readabilityHandler + terminationHandler pattern
  • Rich PATH in CLIBridge env (homebrew, cargo, bun, etc.)
  • Dev mode: uv run --project cli setmac; Bundle mode: Contents/MacOS/setmac-cli

Don't

  • Don't use /usr/bin/env to find uv (GUI apps have minimal PATH)
  • Don't use bytes.lines async iteration on pipes (blocks in some contexts)
  • Don't name anything setmac in the build output dir (collides with Setmac)
  • Don't suggest Xcode for anything
  • Don't hardcode tool lists in Swift or Python
  • Don't use WindowGroup (causes duplicate windows)

Read the full file on GitHub · 47 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. yesterday First seen · 47 lines · 565 tokens per session scan A 0eb6e1e71972

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository v0id-user/setmac (14 stars, last pushed 5mo ago), licensed MIT. It adds 565 tokens to every session, about $0.0028 per session on Opus 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-30.