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/duongductrong/cursor-kitWrote 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/duongductrong/cursor-kit/git)<a href="https://agentmods.dev/rules/duongductrong/cursor-kit/git"><img src="https://agentmods.dev/badge/rules/duongductrong/cursor-kit/git/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.
<a href="https://agentmods.dev/rules/duongductrong/cursor-kit/git"><img src="https://agentmods.dev/badge/rules/duongductrong/cursor-kit/git.svg" alt="Reviewed on agentmods" width="80" 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.00285 | $0.00285 |
| Opus 5.5 | $0.00114 | $0.00114 |
| Sonnet 5.5 | $0.00057 | $0.00057 |
| Haiku 4.5 | $0.00028 | $0.00028 |
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 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.
This is a copy
100% identical to git — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Git Conventions
Commit Messages
Follow Conventional Commits format:
<type>(<scope>): <subject>
[optional body]
[optional footer]
Types
feat: New featurefix: Bug fixdocs: Documentation onlystyle: Code style (formatting, semicolons)refactor: Code change that neither fixes a bug nor adds a featureperf: Performance improvementtest: Adding or updating testschore: Build process, dependencies, tooling
Subject Rules
- Use imperative mood ("add" not "added")
- Don't capitalize first letter
- No period at the end
- Max 50 characters
Examples
feat(auth): add social login with Google
fix(cart): resolve quantity update race condition
docs: update API endpoint documentation
refactor(utils): extract date formatting to shared module
Branch Naming
feature/<description>- New featuresfix/<description>- Bug fixeshotfix/<description>- Urgent production fixeschore/<description>- Maintenance tasks
Pull Request Guidelines
- Keep PRs focused and reasonably sized
- Include clear description of changes
- Reference related issues
- Ensure CI passes before requesting review
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.
- 1mo ago First seen · 52 lines · 285 tokens per session scan A 03b615654cd7
git is a cursor rule published in the GitHub repository duongductrong/cursor-kit (23 stars, last pushed 6mo ago), licensed MIT. It adds 285 tokens to every session, about $0.0011 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to git, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
fusebase-flow-implementation
Fusebase Flow implementation phase rules. Use when editing source code per a locked spec.
git-conventional-commit-messages
Cursor rules for Git development with conventional commit messages integration.
python-github-setup-cursorrules-prompt-file
Cursor rules for Python development with GitHub setup integration.
commit-message-generation-rule
Rules for writing consistent Git commit messages, using labels such as feat for a feature, fix for a bug, and docs for documentation. A commit message records one set of code changes.
atomic-commits
Git best practices - atomic commits, descriptive messages, feature branches.
quality-gates
Enforce quality checks before commits - lint, typecheck, and test affected code.