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/gokulkrishh/.cursorWrote 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/gokulkrishh/.cursor/git)<a href="https://agentmods.dev/rules/gokulkrishh/.cursor/git"><img src="https://agentmods.dev/badge/rules/gokulkrishh/.cursor/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/gokulkrishh/.cursor/git"><img src="https://agentmods.dev/badge/rules/gokulkrishh/.cursor/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.00005 | $0.00370 |
| Opus 5.5 | $0.00002 | $0.00148 |
| Sonnet 5.5 | $0.00001 | $0.00074 |
| Haiku 4.5 | $0.00001 | $0.00037 |
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.
What it actually says
Use conventional commit format for clear and consistent commit messages.
Format
<type>: <description>
Common Types
feat: New Features
feat: add user authentication
feat: implement dark mode toggle
feat: add payment processing
fix: Bug Fixes
fix: sidebar click issue
fix: login form validation
fix: memory leak in component
chore: Maintenance
chore: upgrade packages
chore: update dependencies
chore: configure build settings
refactor: Code Restructuring
refactor: sidebar for application
refactor: user validation logic
refactor: database queries
docs: Documentation
docs: update README
docs: add API documentation
docs: fix installation guide
style: Code Formatting
style: fix indentation
style: resolve linting errors
style: format with prettier
test: Testing
test: add user login tests
test: fix failing unit tests
test: add integration tests
Examples
feat: add shopping cart functionality
fix: resolve checkout button not working
chore: update React to version 18
refactor: extract reusable components
docs: add component usage examples
style: fix TypeScript linting warnings
test: add form validation tests
Rules
- Use present tense ("add" not "added")
- Keep descriptions under 50 characters
- Start with lowercase after colon
- No period at the end
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 · 91 lines · 5 tokens per session scan A 189657b535eb
git is a cursor rule published in the GitHub repository gokulkrishh/.cursor (3 stars, last pushed 8mo ago), licensed MIT. It adds 5 tokens to every session and 370 once invoked, about $0.0000 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.
Other cursor rules, from other repositories
git
Git workflow — commit format, push policy, and PR process.
commit-sponsors
Every git commit message must acknowledge BetterDesk supporters.
no-ai-contributors
Never add AI tools as git authors or project contributors.
git-discipline
Commit, push, and branching rules. Owns ALL git behavior; other files state only their deviations.
git-commit-standards
Enforce structured Git commit messages.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.