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/rosendolu/cursor-rules-deployWrote 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/rosendolu/cursor-rules-deploy/git-commit-push-agent)<a href="https://agentmods.dev/rules/rosendolu/cursor-rules-deploy/git-commit-push-agent"><img src="https://agentmods.dev/badge/rules/rosendolu/cursor-rules-deploy/git-commit-push-agent/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/rosendolu/cursor-rules-deploy/git-commit-push-agent"><img src="https://agentmods.dev/badge/rules/rosendolu/cursor-rules-deploy/git-commit-push-agent.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.00430 | $0.00430 |
| Opus 5.5 | $0.00172 | $0.00172 |
| Sonnet 5.5 | $0.00086 | $0.00086 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
git-commit-push-agent 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-commit-push-agent — 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.
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: This rule governs the process of committing and pushing changes to git repositories. It should be applied whenever: (1) The user indicates they want to commit or push changes, (2) The user asks about git commit conventions, (3) The user wants to update or save their work to git, or (4) Any git-related commit and push operations are requested. The rule ensures consistent commit message formatting, proper change documentation, and maintainable git history. It's particularly important for maintaining clear project history, facilitating code reviews, and ensuring proper documentation of changes. This rule helps maintain high-quality commit messages that explain both what changed and why, making it easier for both humans and AI to understand the project's evolution. globs: alwaysApply: false
Git Commit and Push Conventions
Critical Rules
- Always run
git add .from the workspace root to stage changes - Review staged changes before committing to ensure no unintended files are included
- Format commit titles as
type: brief descriptionwhere type is one of:- feat: new feature
- fix: bug fix
- docs: documentation changes
- style: formatting, missing semi colons, etc
- refactor: code restructuring
- test: adding tests
- chore: maintenance tasks
- Keep commit title brief and descriptive (max 72 chars)
- Add two line breaks after commit title
- Include a detailed body paragraph explaining:
- What changes were made
- Why the changes were necessary
- Any important implementation details
- End commit message with " -Agent Generated Commit Message"
- Push changes to the current remote branch
Examples
Implemented JWT-based user authentication system with secure password hashing and token refresh functionality. This change provides secure user sessions and prevents unauthorized access to protected routes. The implementation uses bcrypt for password hashing and includes proper token expiration handling.
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 · 46 lines · 430 tokens per session scan A d4cfcf8a2466
git-commit-push-agent is a cursor rule published in the GitHub repository rosendolu/cursor-rules-deploy (37 stars, last pushed 1y ago), licensed MIT. It adds 430 tokens to every session, about $0.0017 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to git-commit-push-agent, differing in 0 lines, and is treated as a copy.
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.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.
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.