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/kensaurus/cursor-kenji/gitgit clone --depth 1 https://github.com/kensaurus/cursor-kenjiWrote 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/kensaurus/cursor-kenji/git)<a href="https://agentmods.dev/rules/kensaurus/cursor-kenji/git"><img src="https://agentmods.dev/badge/rules/kensaurus/cursor-kenji/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.00005 | $0.00246 |
| Opus 5 | $0.00003 | $0.00123 |
| Sonnet 5 | $0.00001 | $0.00049 |
| Haiku 4.5 | $0.00001 | $0.00025 |
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 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 Conventions
Branch Naming
feature/description — New functionality
fix/description — Bug fixes
chore/description — Maintenance, deps, config
refactor/description — Code restructuring
docs/description — Documentation only
Commit Messages
Conventional commit format:
<type>(<scope>): <description>
[optional body with details]
Types: feat, fix, docs, style, refactor, perf, test, chore, ci
Examples:
feat(auth): add Google OAuth loginfix(cart): prevent duplicate items on rapid clicksrefactor(hooks): extract useDebounce from search component
Rules
- Atomic commits — one logical change per commit
- Never commit secrets,
.envfiles, or API keys - Never commit
node_modules/,.next/, build artifacts - Run
npm run buildbefore pushing to main - Squash fixup commits before merging PRs
- Delete feature branches after merge
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 · 40 lines · 5 tokens per session scan A 6b106dda6e26
git is a cursor rule published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 8d ago), licensed MIT. It adds 5 tokens to every session and 246 once invoked, about $0.0000 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_workflow
Git workflow integrated with Task Master for feature development and collaboration.
release-commit-analysis-auto
This rule analyzes commits to determine if they should trigger a version bump. It categorizes conventional and non-conventional commits into Features, Bug Fixes, Breaking Changes, Documentation, and Other. It uses intelligent keyword matching for non-conventional commits and analyzes file changes to help categorize…
git-workflow
Git workflow: commits, branches, PRs, history management.
git-master
Git operations — clean commits, PR prep, conflict resolution, change summaries.
git-workflow
Git workflow: commits, branches, PRs, history management.
new_features
Guidelines for integrating new features into the Task Master CLI.