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/sfc-gh-cconner/support-rules-mcp/11-git-workflowgit clone --depth 1 https://github.com/sfc-gh-cconner/support-rules-mcpWrote 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/sfc-gh-cconner/support-rules-mcp/11-git-workflow)<a href="https://agentmods.dev/rules/sfc-gh-cconner/support-rules-mcp/11-git-workflow"><img src="https://agentmods.dev/badge/rules/sfc-gh-cconner/support-rules-mcp/11-git-workflow.svg" alt="Measured on agentmods" 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 | $0.01984 | $0.01984 |
| Opus 5 | $0.00992 | $0.00992 |
| Sonnet 5 | $0.00397 | $0.00397 |
| Haiku 4.5 | $0.00198 | $0.00198 |
Grade A, and why
11-git-workflow 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 — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow Standards
PURPOSE: Git workflow, branching, and commit standards for maintaining code quality.
✍️ Git & Branching Workflow
Branch Management
- Always create a new branch before starting work
- Branch names should reflect the feature or fix:
feature/description,fix/issue-name,docs/update-readme - Keep branches focused on a single feature or fix
- Delete branches after merging to keep repository clean
Commit Standards
- Always commit using semantic commit messages:
feat:,fix:,docs:,chore:,test: - Write clear, descriptive commit messages
- Make atomic commits - each commit should represent a single logical change
- DO NOT manually update version numbers - let automated tools handle versioning
Semantic Commit Format
<type>: <description>
[optional body]
[optional footer]
Types:
feat:- New features or rulesfix:- Bug fixesdocs:- Documentation changeschore:- Maintenance taskstest:- Test additions/modificationsrefactor:- Code refactoringstyle:- Code style changes
Examples
git commit -m "feat: add snowflake-cli rule for Snowhouse connections"
git commit -m "fix: correct DPO mapping for image repositories"
git commit -m "docs: update README with new rules structure"
git commit -m "test: add validation for MCP server rules"
git commit -m "refactor: reorganize core rules into logical groups"
📦 Code Quality & Formatting
Pre-commit Requirements
- Code must pass all linting and formatting checks
- Use project's configured formatters (Black, Prettier, etc.)
- Follow language-specific best practices (PEP 8 for Python, etc.)
- Use type hints/annotations where the language supports them
- Write clear, self-documenting code with appropriate comments
Quality Checks
# Run all pre-commit hooks
pre-commit run --all-files
# Run specific checks
black --check .
isort --check-only .
flake8 .
File Management
- Always update/maintain CODEOWNERS when setting up or modifying projects
- Handle with care core configuration files
- Always check PROJECT_HISTORY.md or CHANGELOG.md before making changes
- Update documentation when adding new features or rules
- Clean up temporary files and unused resources
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 · 311 lines · 1,984 tokens per session scan A 5ef935ae43b0
11-git-workflow is a cursor rule published in the GitHub repository sfc-gh-cconner/support-rules-mcp (0 stars, last pushed 10mo ago), licensed Apache-2.0. It adds 1,984 tokens to every session, about $0.0099 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-31.
Other cursor rules, from other repositories
git
Conventional commit message format for git commits.
git
辅助生成 Git 提交信息和执行 Git 命令.
no-ai-attribution
Never attribute commits, comments, or contributions to AI agents.
develop-feature
Develop a feature end-to-end from design to PR. Invoke when the user asks to build, develop, or ship a complete feature.
git-commit-attribution
Git commits must use the human developer identity only; never Cursor Agent co-authorship.
commit-and-push
Commit (conventional commit) files and push to the remote repository.