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/mamahoos/dot-filesWrote 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/mamahoos/dot-files/git-workflow-and-versioning)<a href="https://agentmods.dev/rules/mamahoos/dot-files/git-workflow-and-versioning"><img src="https://agentmods.dev/badge/rules/mamahoos/dot-files/git-workflow-and-versioning/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/mamahoos/dot-files/git-workflow-and-versioning"><img src="https://agentmods.dev/badge/rules/mamahoos/dot-files/git-workflow-and-versioning.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.00418 | $0.00418 |
| Opus 5.5 | $0.00167 | $0.00167 |
| Sonnet 5.5 | $0.00084 | $0.00084 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
git-workflow-and-versioning 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.
What it actually says
Git Workflow and Versioning
Applies to any coding change in any workspace this rule is installed in. Procedures and examples: .cursor/skills/git-workflow-and-versioning/SKILL.md.
Atomic commits (mandatory)
One logical change per commit, in every repo. Many small commits, never one large mixed commit. Commit after each verified slice without being asked; do not wait.
- After you write a hunk, commit it before you edit it again. One hunk → one
git apply --index(or equivalent) → one commit. - Rewriting a line you wrote but have not committed is a second change: commit the current tree, then edit, then commit the edit. Do not fold a write + rewrite + formatting pass into one dirty blob.
- Do not
git commit --amendto hide a second change unless the user asked and amend is allowed. - Do not mix refactor + feature + formatting.
- Message prefix:
feat,fix,refactor,test,docs,chore. - Before committing: review the staged diff and run relevant tests/lint.
Branches
Tiny isolated fixes go on the active branch. Non-trivial work (multi-file, risky refactor, experiment, parallel work) gets its own branch first: feature/ | fix/ | refactor/ | chore/ + short description. Keep main stable and branches short-lived.
Sync with the base branch often, re-verify after resolving conflicts, and never force-push a shared branch unless asked.
Scope
Commit only files belonging to the current task; never .env, secrets, build artifacts, or unrelated generated files. If unrelated local changes exist, keep them out of the commit. In summaries, state what changed and what was intentionally left untouched.
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 Changed · -18 lines · +34 tokens per session 41f7053d69f6
- 1mo ago First seen · 48 lines · 384 tokens per session scan A 735b3fd5b062
git-workflow-and-versioning is a cursor rule published in the GitHub repository mamahoos/dot-files (5 stars, last pushed 2d ago), licensed MIT. It adds 418 tokens to every session, about $0.0017 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-31.
Other cursor rules, from other repositories
git
Git rules. Conventional commits, atomic staging, no force push.
release-ts-sdk
Release @aptos-labs/ts-sdk or @aptos-labs/confidential-asset — version bump, changelog stamp, release PR, then tag + GitHub Release that triggers NPM publish.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.
40-git-safety
Git safety rule for branches, commits, pushes, and destructive Git commands.
git-master
Git operations — clean commits, PR prep, conflict resolution, change summaries.
git-workflow
Git branching and PR workflow.