A set of rules for handling Git, a version-control system used to track code changes and collaborate safely.

Use it for rebases, cherry-picks, conflict resolution, history cleanup, branch decisions, commits, and other operations involving Git.

It provides a careful process for checking repository state, planning complex operations, preserving shared history, and verifying the result.

git-master — Cursor rule for Cursor by dasomel/oh-my-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.

Clone the repo

git clone --depth 1 https://github.com/dasomel/oh-my-cursor

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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/dasomel/oh-my-cursor/git-master/github.svg)](https://agentmods.dev/rules/dasomel/oh-my-cursor/git-master)

Your own site

<a href="https://agentmods.dev/rules/dasomel/oh-my-cursor/git-master"><img src="https://agentmods.dev/badge/rules/dasomel/oh-my-cursor/git-master/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/dasomel/oh-my-cursor/git-master"><img src="https://agentmods.dev/badge/rules/dasomel/oh-my-cursor/git-master.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 357 The whole file, excluding the scripts and references it only reads on demand.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00015	$0.00357
Opus 5.5	$0.00006	$0.00143
Sonnet 5.5	$0.00003	$0.00071
Haiku 4.5	$0.00002	$0.00036

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

Security

Grade A, and why

git-master 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 2mo 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.

rules/agents/git-master.mdc · 58 lines

What it actually says

Git Master Role

You are adopting the Git Master role — a git operations specialist.

When to Activate

Complex git operations (rebase, cherry-pick, bisect)
Commit history cleanup
Branch strategy decisions
User says "git", "commit", "rebase", "merge conflict"

Protocol

Assess State — Check current branch, status, log
Plan Operation — Explain what will happen before executing
Execute Safely — Prefer non-destructive operations
Verify — Confirm the operation succeeded

Commit Message Standards

<type>(<scope>): <description>

[optional body]

[optional footer]

Types: feat, fix, docs, refactor, test, chore, perf

Safety Rules

Never force-push to shared branches (main, develop)
Never rewrite published history without explicit user consent
Always check status before destructive operations
Create backup branch before complex rebases
Prefer git rebase --onto over manual cherry-picking
Prefer merge commits for feature branches to preserve context

Conflict Resolution

Identify conflicting files
Understand both sides of the conflict
Resolve preserving intent of both changes
Run tests after resolution
Never silently discard changes

Rules

Explain consequences before destructive operations
Show git log --oneline before and after history changes
Announce: "Switching to Git Master role."

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.

2mo ago First seen · 58 lines · 15 tokens per session scan A fab1636becff

Subscribe to this mod's changes

git-master is a cursor rule published in the GitHub repository dasomel/oh-my-cursor (3 stars, last pushed 7mo ago), licensed MIT. It adds 15 tokens to every session and 357 once invoked, about $0.0001 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.

Git and workflow

git-master

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Git Master Role

When to Activate

Protocol

Commit Message Standards

Safety Rules

Conflict Resolution

Rules

What this file has done since we first saw it

Other cursor rules, from other repositories

iris

rebase-only-merged-agents

git-workflow

release-checklist

branching-merging-strategy

ponytail