agentmods.dev

git-master

git-master is a cursor rule for Cursor from Jkudjo/oh-my-cursor. It costs 14 tokens per session (489 once invoked), scanned A, original, MIT.

A rule set for Git work, including clean commits, pull-request preparation, and conflict resolution. Git is the version-control system used to track code changes and collaborate safely.

In plain words
What is it for?
Use it to inspect changes, create conventional commit messages, prepare pull-request summaries, check test status, or identify and resolve merge conflicts.
Why use it?
It helps keep commits focused, prevents secrets or unrelated files from being included, and makes changes easier to review.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

not rated 1repo 6mo ago A scan 14 tokens original MIT

Good fit Use it to inspect changes, create conventional commit messages, prepare pull-request summaries, check test status, or identify and resolve merge conflicts.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/jkudjo/oh-my-cursor/git-master
View source ↗ Jkudjo/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/Jkudjo/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.

agentmods badge for git-master

README.md
[![agentmods](https://agentmods.dev/badge/rules/jkudjo/oh-my-cursor/git-master/github.svg)](https://agentmods.dev/rules/jkudjo/oh-my-cursor/git-master)
Your own site
<a href="https://agentmods.dev/rules/jkudjo/oh-my-cursor/git-master"><img src="https://agentmods.dev/badge/rules/jkudjo/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.

agentmods 80×15 button for git-master

Your own site · 80×15
<a href="https://agentmods.dev/rules/jkudjo/oh-my-cursor/git-master"><img src="https://agentmods.dev/badge/rules/jkudjo/oh-my-cursor/git-master.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 489 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00014 $0.00489
Opus 5.5 $0.00006 $0.00196
Sonnet 5.5 $0.00003 $0.00098
Haiku 4.5 $0.00001 $0.00049

Measured 1mo ago against content hash 33de1f112f27, 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 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.

rules/git-master.mdc · 62 lines

What it actually says

@git-master

Trigger: Any git workflow operation.

Operations

@git-master clean-commit

  1. Review staged/unstaged changes — remove debug code, console.logs, commented-out code.
  2. Stage only relevant files. Never stage: .env, secrets, unrelated changes.
  3. Write commit message in conventional format:
    • feat(scope): short description — new capability
    • fix(scope): short description — bug fix
    • refactor(scope): short description — no behavior change
    • test(scope): short description — tests only
    • docs(scope): short description — docs only
    • chore(scope): short description — tooling, deps
  4. Body (if needed): explain WHY, not what. The diff shows what.
  5. Run: git commit -m "$(cat <<'EOF' ... EOF)"

@git-master prep-pr

  1. git log base..HEAD — list all commits in this branch.
  2. git diff base...HEAD — full diff.
  3. Write PR description: 
    ## What
[1-3 bullet points]

## Why
[motivation / linked issue]

## How
[approach, key decisions]

## Test plan
- [ ] item
  4. Verify checklist: no secrets, no debug code, tests pass, no unintended files.

@git-master resolve-conflicts

  1. List conflicted files: git diff --name-only --diff-filter=U
  2. For each conflict: read both sides carefully before choosing.
  3. Merge intent of both when possible. Flag any that need human judgment.
  4. After resolving: run tests to verify.

@git-master summarize

  1. git log --oneline base..HEAD
  2. Group changes: Features | Fixes | Refactors | Breaking changes
  3. Write a clean changelog section.

Rules

  • Never force-push to main/master.
  • Never commit secrets, tokens, or credentials.
  • Conventional commits format — always.
  • PR is not "ready" until tests pass and checklist is clean.
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 · 62 lines · 14 tokens per session scan A 33de1f112f27

Subscribe to this mod's changes

git-master is a cursor rule published in the GitHub repository Jkudjo/oh-my-cursor (1 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 489 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.

CommitsGit and workflowReleasesagentai-workflowcodexcursorcursor-aicursor-rules
Related

Other cursor rules, from other repositories

release-commit-analysis-auto

This rule analyzes commits to determine if they should trigger a version bump. It categorizes conventional and non-conventional commits into Features, Bug Fixes, Breaking Changes, Documentation, and Other. It uses intelligent keyword matching for non-conventional commits and analyzes file changes to help categorize…

usrrname/cursorrules · 0 tokens

git-workflow

Git workflow: commits, branches, PRs, history management.

nedcodes-ok/cursorrules-collection · 891 tokens

changelog-generator-manual

This rule generates a comprehensive changelog.md file by analyzing all git tags and commits, creating a chronological record of all project changes with proper semantic versioning structure. The changelog.md file is stored at the root of the project.

usrrname/cursorrules · 0 tokens

release-git-tags-auto

This rule checks for existing tags before creating new ones. It also offers to push the tag to the remote repository. It runs when users request release creation, version bumping, or package publishing.

usrrname/cursorrules · 0 tokens

release-validation-auto

This rule validates release prerequisites including branch naming conventions and package.json structure. It runs when users request release creation, version bumping, or package publishing. The rule ensures releases only occur from appropriate branches (release/, hotfix/, fix/) and validates package.json exists with…

usrrname/cursorrules · 0 tokens

release-version-bump-auto

Apply when the user is creating or preparing a release, version bump, tag, publish, or deploy. Validates semantic version bumps against change analysis (breaking/feat/fix), blocks inappropriate bumps, and guides major/minor/patch or custom version choice. Use for release workflows, package versioning, and…

usrrname/cursorrules · 67 tokens