agentmods.dev

git-flow

git-flow is a cursor rule for Cursor from quinnjr/google-mcp. It costs 750 tokens per session, scanned A, original, MIT.

A Git workflow that separates production code, shared development work, features, bug fixes, releases, and emergency fixes into named branches.

In plain words
What is it for?
It guides branch naming, release preparation, hotfixes, and conventional commits for projects using the Git-flow model.
Why use it?
It gives a team predictable places for different kinds of work and consistent commit messages.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

not rated 11repo 1mo ago A scan 750 tokens original MIT

Good fit It guides branch naming, release preparation, hotfixes, and conventional commits for projects using the Git-flow model.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/quinnjr/google-mcp/git-flow
View source ↗ quinnjr/google-mcp
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.

Clone the repo
git clone --depth 1 https://github.com/quinnjr/google-mcp

Made for: Cursor.

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

agentmods badge for git-flow

README.md
[![agentmods](https://agentmods.dev/badge/rules/quinnjr/google-mcp/git-flow/github.svg)](https://agentmods.dev/rules/quinnjr/google-mcp/git-flow)
Your own site
<a href="https://agentmods.dev/rules/quinnjr/google-mcp/git-flow"><img src="https://agentmods.dev/badge/rules/quinnjr/google-mcp/git-flow/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.

agentmods 80×15 button for git-flow

Your own site · 80×15
<a href="https://agentmods.dev/rules/quinnjr/google-mcp/git-flow"><img src="https://agentmods.dev/badge/rules/quinnjr/google-mcp/git-flow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 750 This file is loaded in full into every session.
When invoked 750 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found 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.1 $0.00750 $0.00750
Opus 5.5 $0.00300 $0.00300
Sonnet 5.5 $0.00150 $0.00150
Haiku 4.5 $0.00075 $0.00075

Measured 1mo ago against content hash c5d750efdcbf, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

git-flow 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.

.cursor/rules/git-flow.mdc · 121 lines

How it starts

The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Git-Flow Workflow

This repository follows the git-flow branching model.

Branch Types

Branch Purpose Naming Convention
main Production-ready code Protected, only merges from release/hotfix
develop Integration branch for features Protected
feature/* New features feature/short-description
bugfix/* Bug fixes for develop bugfix/short-description
release/* Release preparation release/vX.Y.Z
hotfix/* Production emergency fixes hotfix/short-description

Commit Message Format

Use conventional commits format:

<type>(<scope>): <subject>

[optional body]

[optional footer]

Types

  • feat: New feature
  • fix: Bug fix
  • docs: Documentation only
  • style: Code style (formatting, semicolons, etc.)
  • refactor: Code refactoring (no feature/fix)
  • perf: Performance improvement
  • test: Adding/updating tests
  • chore: Build process, dependencies, tooling
  • ci: CI/CD changes

Scopes (for this project)

  • auth: OAuth authentication
  • drive: Google Drive service
  • docs: Google Docs service
  • sheets: Google Sheets service
  • calendar: Google Calendar service
  • gmail: Gmail service
  • contacts: People/Contacts service
  • youtube: YouTube service
  • slides: Google Slides service
  • tasks: Google Tasks service
  • server: MCP server core
  • types: Type definitions

Examples

feat(calendar): add recurring event support

fix(auth): handle token refresh failure gracefully

chore(deps): update googleapis to v145

docs: update README with new setup instructions

Workflow

  1. Starting a feature:

    git checkout develop
git pull origin develop
git checkout -b feature/my-feature

  2. Completing a feature:

    git checkout develop
git merge --no-ff feature/my-feature
git push origin develop
git branch -d feature/my-feature

  3. Creating a release:

    git checkout develop
git checkout -b release/v1.2.0
# bump version, final fixes
git checkout main
git merge --no-ff release/v1.2.0
git tag -a v1.2.0
git checkout develop
git merge --no-ff release/v1.2.0

Read the full file on GitHub · 121 lines

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. 1mo ago First seen · 121 lines · 750 tokens per session scan A c5d750efdcbf

Subscribe to this mod's changes

git-flow is a cursor rule published in the GitHub repository quinnjr/google-mcp (11 stars, last pushed 1mo ago), licensed MIT. It adds 750 tokens to every session, about $0.0030 per session on Opus 5.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-08-30.

Git and workflowaiclaudecursorgmailgooglegoogle-calendar
Related

Other cursor rules, from other repositories

cd

GitHub Actions CD - called by release.yml after the tag, no push-tags trigger, cf workers versions create then a 100% deployment in deployOrder, scoped API token on the production environment, GitHub-owned deployment record.

louisbrulenaudet/monorepo-template · 0 tokens

nauro-ship-task

Run the full planner -> executor -> reviewer -> tech-lead -> direct-user-confirm -> push chain through Cursor's native project workflow agents. Requires the four bundled .cursor/agents/nauro-.md definitions and fails closed without native dispatch.

Nauro-AI/nauro · 49 tokens

handoff

Export a Waybill Bundle by default, or import one when explicitly requested.

wardmos/waybill · 15 tokens

conventional-commits

Conventional Commits mapped to SemVer; use this repo's types and scopes for commit and PR titles.

jamro/tiny-engineer · 524 tokens

git-conventions

Git workflow and commit conventions for AI-assisted development.

vibestackdev/vibe-stack · 0 tokens

roslyn-mcp-version-bump

Auto-bump Version after successful MCP self-build and reload.

VuDZ/RoslynMcpServer · 524 tokens