branch-dev-main

branch-dev-main is a cursor rule for Cursor from opensquad-ai/opensquad. It costs 187 tokens per session, scanned A, original, MIT.

A Git branch workflow that uses `dev` for development and `main` for verified releases. A branch is a separate line of code changes in a Git repository.

In plain words
What is it for?
Use it to guide branch checkout, pulling changes, testing, merging, and pushing both branches after development.
Why use it?
It reduces accidental work on the release branch and prevents `dev` and `main` from drifting apart.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it to guide branch checkout, pulling changes, testing, merging, and pushing both branches after development.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/opensquad-ai/opensquad/branch-dev-main
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.

Clone the repo
git clone --depth 1 https://github.com/opensquad-ai/opensquad

Made for: Cursor.

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

agentmods badge for branch-dev-main

README.md
[![agentmods](https://agentmods.dev/badge/rules/opensquad-ai/opensquad/branch-dev-main/github.svg)](https://agentmods.dev/rules/opensquad-ai/opensquad/branch-dev-main)
Your own site
<a href="https://agentmods.dev/rules/opensquad-ai/opensquad/branch-dev-main"><img src="https://agentmods.dev/badge/rules/opensquad-ai/opensquad/branch-dev-main/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.

agentmods 80×15 button for branch-dev-main

Your own site · 80×15
<a href="https://agentmods.dev/rules/opensquad-ai/opensquad/branch-dev-main"><img src="https://agentmods.dev/badge/rules/opensquad-ai/opensquad/branch-dev-main.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 187 This file is loaded in full into every session.
When invoked 187 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00187 $0.00187
Opus 5.5 $0.00075 $0.00075
Sonnet 5.5 $0.00037 $0.00037
Haiku 4.5 $0.00019 $0.00019

Measured 1mo ago against content hash 8804822af327, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

branch-dev-main 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.

.cursor/rules/branch-dev-main.mdc · 12 lines

What it actually says

Branch workflow (dev → main)

  • Default branch for all development: dev. Before starting work, check out dev and pull; do not commit feature work on main.
  • After changes are tested and look good: merge dev into main (fast-forward when possible) and push both origin/dev and origin/main so they stay aligned.
  • After any update/push: ensure dev and main point at the same commit (or merge immediately); do not leave them diverged.
  • Prefer: develop on dev → verify → merge to main → push both. Avoid developing on main then back-merging to dev unless recovering from an accidental main-only push.
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. 1mo ago First seen · 12 lines · 187 tokens per session scan A 8804822af327

Subscribe to this mod's changes

branch-dev-main is a cursor rule published in the GitHub repository opensquad-ai/opensquad (7 stars, last pushed 7d ago), licensed MIT. It adds 187 tokens to every session, about $0.0007 per session on Opus 5.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-31.