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.
npx agentmods add rules/dasomel/oh-my-cursor/git-mastergit clone --depth 1 https://github.com/dasomel/oh-my-cursorWhat 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 | $0.00015 | $0.00357 |
| Opus 5 | $0.00008 | $0.00179 |
| Sonnet 5 | $0.00003 | $0.00071 |
| Haiku 4.5 | $0.00002 | $0.00036 |
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 2d 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.
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 --ontoover 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 --onelinebefore and after history changes - Announce: "Switching to Git Master role."
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.
- 2d ago First seen · 58 lines · 15 tokens per session scan A fab1636becff
git-master is a cursor rule published in the GitHub repository dasomel/oh-my-cursor (2 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 357 once invoked, about $0.0001 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-31.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.