awesome-cursor-rules-mdc is a generator that creates Cursor MDC rule files from structured library information, using semantic search and language models to gather and organize guidance. Developers use it to produce reusable rules for libraries in Cursor, and the catalogue includes 200 of those rules.
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.
git clone --depth 1 https://github.com/sanjeed5/awesome-cursor-rules-mdcWrote 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.
[](https://agentmods.dev/rules/sanjeed5/awesome-cursor-rules-mdc/git)<a href="https://agentmods.dev/rules/sanjeed5/awesome-cursor-rules-mdc/git"><img src="https://agentmods.dev/badge/rules/sanjeed5/awesome-cursor-rules-mdc/git.svg" alt="Measured on agentmods" height="20"></a>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.02065 | $0.02065 |
| Opus 5 | $0.01033 | $0.01033 |
| Sonnet 5 | $0.00413 | $0.00413 |
| Haiku 4.5 | $0.00206 | $0.00206 |
Grade A, and why
git 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Best Practices
Git is the backbone of our development workflow. Adhering to these practices ensures a clean, readable history, minimizes conflicts, and enables rapid, reliable delivery. These are non-negotiable standards.
1. Branching Strategy: Feature-Branch Workflow
We use a feature-branch workflow with short-lived branches. All development happens on dedicated branches, never directly on main or develop.
mainbranch: Always production-ready. Only merges from release branches or squashed feature branches are allowed. Protected.developbranch: Integrates completed features. Protected.- Feature branches: Created from
develop, short-lived, for a single feature or bug fix. Merged intodevelopvia Pull Requests (PRs).
Guideline: Branch Naming
Name branches clearly and consistently, linking directly to a ticket or feature.
❌ BAD:
git checkout -b my-feature
git checkout -b fix
✅ GOOD:
# For a new feature (e.g., JIRA ticket FEAT-123)
git checkout -b feat/FEAT-123-add-user-profile
# For a bug fix (e.g., JIRA ticket BUG-456)
git checkout -b fix/BUG-456-auth-redirect-loop
# For a refactor
git checkout -b refactor/improve-logging-middleware
2. Commit Messages: Conventional Commits
Every commit message must follow the Conventional Commits specification. This enables automated changelog generation and semantic versioning.
Format: <type>(<scope>): <description>
type:feat,fix,docs,style,refactor,perf,test,build,ci,chore,revert.scope(optional): The part of the codebase affected (e.g.,auth,api,ui,database).description: Concise, imperative, present tense. Max 50 characters.- Body (optional): More detailed explanation, breaking changes, references to issues.
Guideline: Write Clear, Atomic Commits
Each commit should represent a single logical change.
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.
- 4d ago First seen · 258 lines · 2,065 tokens per session scan A 01f1286d67f1
git is a cursor rule published in the GitHub repository sanjeed5/awesome-cursor-rules-mdc (3,571 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 2,065 tokens to every session, about $0.0103 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-09-03.
Other cursor rules, from other repositories
git
Conventional commit message format for git commits.
git-commit-attribution
Git commits must use the human developer identity only; never Cursor Agent co-authorship.
commit-sponsors
Every git commit message must acknowledge BetterDesk supporters.
git_workflow
Git Workflow and Configuration for AGB SDK.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.
git-commits
description: "Reference and apply the git commits skill for Conventional Commit formatting and pre-push checks." alwaysApply: true.