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/ivangrynenko/cursorrulesWrote 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/ivangrynenko/cursorrules/git-commit-standards)<a href="https://agentmods.dev/rules/ivangrynenko/cursorrules/git-commit-standards"><img src="https://agentmods.dev/badge/rules/ivangrynenko/cursorrules/git-commit-standards/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/ivangrynenko/cursorrules/git-commit-standards"><img src="https://agentmods.dev/badge/rules/ivangrynenko/cursorrules/git-commit-standards.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.00377 |
| Opus 5.5 | $0.00000 | $0.00151 |
| Sonnet 5.5 | $0.00000 | $0.00075 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
git-commit-standards 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 Commit Standards
Ensures consistent Git commit messages.
Rule Details
-
Name: git_commit_standards
-
Description: Enforce structured Git commit messages.
Filters
- file extension pattern:
\\.git/.*
Enforcement Checks
- Conditions:
- pattern
^(?!fix|feat|perf|docs|style|refactor|test|chore):– Use a commit message prefix followed by colon and space (fix:, feat:, etc.).- More precise regex to ensure prefix is followed by colon and space
- pattern
^(fix|feat|perf|docs|style|refactor|test|chore): [A-Z]– First word after prefix should be lowercase.- Check for uppercase after the prefix
- pattern
^(fix|feat|perf|docs|style|refactor|test|chore): .{46,}– Keep commit message content (excluding prefix) under 46 characters.- More precise length check that excludes the prefix from the count
- pattern
^(fix|feat|perf|docs|style|refactor|test|chore):(?! )– Include a space after the colon in prefix.- Ensure there's a space after the colon
- pattern
Suggestions
- Guidance: Recommended commit format:
- "fix: resolved bug in user authentication"
- "feat: added new search functionality"
- "docs: updated installation guide"
- "style: fixed button alignment"
- "refactor: simplified login logic"
- "test: added unit tests for auth"
- "chore: updated dependencies"
- "perf: optimized database queries"
Metadata
- Priority: high
- Version: 1.2
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 · 44 lines · 0 tokens per session scan A 958ee9a1a620
git-commit-standards is a cursor rule published in the GitHub repository ivangrynenko/cursorrules (88 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 377 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
git-workflow
Git workflow: commits, branches, PRs, history management.
git-commit-conventions
Cursor rule "git-commit-conventions" from brettdavies/cursor-template, covering commit message conventions, mandatory process sequence, 1. capture changes [required], 2. process diff file [required] and 3. generate commit message [required].
git-workflow
Step-by-step instructions for Git workflow, including branch management, commits, and PR process.
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
Reviews working-tree changes, then drafts a Conventional Commits title/body and states the semantic-release version bump a single such commit would imply. Also notes which defensive-code categories were touched. Use when the user wants to commit recent work, prepare a Conventional Commits message, or asks for…