git-commit-push-agent

A set of rules for saving code changes in Git, a system that tracks versions of files, and sending them to a shared repository.

In plain words
What is it for?
It guides staging, reviewing, writing commit messages, committing, and pushing changes to the current remote branch.
Why use it?
It keeps commit messages consistent and helps prevent unintended files from being saved or shared.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/moclam1905/cocktailrecipes/git-commit-push-agent
Clone the repo
git clone --depth 1 https://github.com/moclam1905/CocktailRecipes

Made for: Cursor.

Per session 430 This file is loaded in full into every session.
When invoked 430 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00430 $0.00430
Opus 5 $0.00215 $0.00215
Sonnet 5 $0.00086 $0.00086
Haiku 4.5 $0.00043 $0.00043

Measured yesterday against content hash d4cfcf8a2466, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

Origin

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.

.cursor/rules/tool-rules/git-commit-push-agent.mdc · 46 lines

What it actually says

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 description where 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.

-Agent Generated Commit Message

fixed some bugs and added features

Changes

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.

  1. yesterday First seen · 46 lines · 430 tokens per session scan A d4cfcf8a2466

Subscribe to this mod's changes

git-commit-push-agent is a cursor rule published in the GitHub repository moclam1905/CocktailRecipes (1 stars, last pushed 1y ago), licensed MIT. It adds 430 tokens to every session, about $0.0022 per session on Opus 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.

Related

Other cursor rules, from other repositories

android-project

Core behavior rules for AI agents working on this Android project.

JoDaBaRo/agentic-mobile-rules · 8,084 tokens

android-project-bootstrap

Walks a developer through bootstrapping a BRAND-NEW Android project for agentic CLI delivery — creating the Firebase project, registering the Android app, setting up App Distribution, creating the Google Play Console listing, wiring API access, and installing the Gradle plugins. Use when the user says they're starting…

JoDaBaRo/agentic-mobile-rules · 106 tokens

ios-project-bootstrap

Walks a developer through bootstrapping a BRAND-NEW iOS project for agentic CLI delivery — Apple Developer Program enrollment, App Store Connect listing, provisioning profiles, Fastlane setup from scratch, Firebase App Distribution, TestFlight + App Store first upload. Use when the user says they're starting a new iOS…

JoDaBaRo/agentic-mobile-rules · 108 tokens

android-project-onboarding

Walks a new developer through one-time setup of an EXISTING configured Android project from a blank macOS install — JDK, Android SDK, AVD, scrcpy, shell env vars, credential files, and a smoke-test build. Assumes Firebase project + Play Console listing already exist; user just needs to acquire credentials. Use when…

JoDaBaRo/agentic-mobile-rules · 161 tokens

ios-project-onboarding

Walks a new developer through one-time setup of an EXISTING configured iOS project from a blank macOS install — Xcode, Fastlane, SPM dependencies, code signing, simulator, and a smoke-test build. Assumes App Store Connect + Firebase + Fastlane are already configured upstream; user just needs local toolchain +…

JoDaBaRo/agentic-mobile-rules · 182 tokens

ios-project

Core behavior rules for AI agents working on this iOS project.

JoDaBaRo/agentic-mobile-rules · 4,506 tokens