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/quinnjr/google-mcp/git-flowgit clone --depth 1 https://github.com/quinnjr/google-mcpWhat 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 | $0.00750 | $0.00750 |
| Opus 5 | $0.00375 | $0.00375 |
| Sonnet 5 | $0.00150 | $0.00150 |
| Haiku 4.5 | $0.00075 | $0.00075 |
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 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.
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 featurefix: Bug fixdocs: Documentation onlystyle: Code style (formatting, semicolons, etc.)refactor: Code refactoring (no feature/fix)perf: Performance improvementtest: Adding/updating testschore: Build process, dependencies, toolingci: CI/CD changes
Scopes (for this project)
auth: OAuth authenticationdrive: Google Drive servicedocs: Google Docs servicesheets: Google Sheets servicecalendar: Google Calendar servicegmail: Gmail servicecontacts: People/Contacts serviceyoutube: YouTube serviceslides: Google Slides servicetasks: Google Tasks serviceserver: MCP server coretypes: 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
-
Starting a feature:
git checkout develop git pull origin develop git checkout -b feature/my-feature -
Completing a feature:
git checkout develop git merge --no-ff feature/my-feature git push origin develop git branch -d feature/my-feature -
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
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 · 121 lines · 750 tokens per session scan A c5d750efdcbf
git-flow is a cursor rule published in the GitHub repository quinnjr/google-mcp (11 stars, last pushed 4d ago), licensed MIT. It adds 750 tokens to every session, about $0.0037 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-08-30.
Other cursor rules, from other repositories
archcore-files
Enforce MCP-only operations when working with .archcore/ files.
dev_workflow
Guide for using Taskmaster to manage task-driven development workflows.
execution
Repository execution and verification commands.
cosmosmith
Cosmosmith project rules adapter.
no-crux-frontmatter
This is a regular rule file that does not have crux: true in its frontmatter. It should be ignored by the CRUX compression hook.
fix-issue
Implement a fix following the human-thinking loop — understand the root cause, plan the minimal change, implement, verify the problem is actually gone.