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/Pranav-Karra-3301/tuckWrote 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/pranav-karra-3301/tuck/git)<a href="https://agentmods.dev/rules/pranav-karra-3301/tuck/git"><img src="https://agentmods.dev/badge/rules/pranav-karra-3301/tuck/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/pranav-karra-3301/tuck/git"><img src="https://agentmods.dev/badge/rules/pranav-karra-3301/tuck/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.00000 | $0.00428 |
| Opus 5.5 | $0.00000 | $0.00171 |
| Sonnet 5.5 | $0.00000 | $0.00086 |
| Haiku 4.5 | $0.00000 | $0.00043 |
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
Git Rules
Branch Strategy
main- Production-ready, protectedfeat/*- New featuresfix/*- Bug fixesdocs/*- Documentationrefactor/*- Code restructuring
Before Starting Work
ALWAYS sync with main:
git checkout main
git fetch origin
git pull origin main
git checkout -b feat/your-feature
Commit Messages
Follow Conventional Commits:
<type>(<scope>): <description>
[optional body]
[optional footer]
Types
| Type | Description | Version Bump |
|---|---|---|
feat |
New feature | Minor (0.x.0) |
fix |
Bug fix | Patch (0.0.x) |
docs |
Documentation | None |
style |
Formatting | None |
refactor |
Restructuring | None |
perf |
Performance | Patch |
test |
Tests | None |
chore |
Maintenance | None |
Examples
feat: add restore command for backup recovery
fix: handle missing config file gracefully
docs: update installation instructions
refactor: extract git operations to lib/git.ts
test: add integration tests for sync command
chore: update dependencies
Breaking Changes
feat!: redesign configuration format
BREAKING CHANGE: Config files must be migrated
Before Committing
Run all checks:
pnpm lint && pnpm typecheck && pnpm test
Pull Requests
- Create against
main - Wait for CI to pass
- Request review
- Address feedback
- Merge when approved
NEVER Do
- Force push to main
- Skip CI checks
- Merge without review
- Commit directly to main
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 · 0 tokens per session scan A edc011007c6e
git is a cursor rule published in the GitHub repository Pranav-Karra-3301/tuck (15 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 428 tokens. 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-30.
Other cursor rules, from other repositories
semver-changelog-agent
Apply when versioning software releases, maintaining changelogs, or setting up automated release processes (like semantic-release). Enforces strict Semantic Versioning (MAJOR.MINOR.PATCH), maintaining a clear CHANGELOG.md (e.g., Keep a Changelog format), and potentially using conventional commits for automation.…
github-workflow
GitHub invariants — standard flow on listed use cases; no issue spam; tick linked checklists before merge.
commit-and-push
Commit (conventional commit) files and push to the remote repository.
git
Cursor rule "git" from duongductrong/antigravity-kit, covering git conventions, commit messages, types, subject rules and examples.
release-checklist
What to update with each code change or version release.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.