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/mamahoos/dot-files/git-workflow-and-versioninggit clone --depth 1 https://github.com/mamahoos/dot-filesWhat 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.00384 | $0.00384 |
| Opus 5 | $0.00192 | $0.00192 |
| Sonnet 5 | $0.00077 | $0.00077 |
| Haiku 4.5 | $0.00038 | $0.00038 |
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 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.
What it actually says
Git Workflow and Versioning
Apply this workflow for any coding change in this repository.
Use .cursor/skills/git-workflow-and-versioning/SKILL.md for detailed procedures and examples.
Default Behavior
- Keep changes small and incremental.
- After each completed and verified slice, create a commit.
- Prefer many small atomic commits over one large commit.
- Keep
mainstable; do not keep long-running feature branches.
Commit Rules
- One logical change per commit.
- Use descriptive commit messages with a type prefix:
feat,fix,refactor,test,docs,chore. - Do not mix refactor + feature + formatting in one commit.
- Before commit: review staged diff, run relevant tests/lint, and avoid committing secrets.
Branch Rules
- For tiny and isolated fixes, commit directly on the active working branch.
- For non-trivial tasks (multi-file changes, risky refactors, experiments, parallel work), create a dedicated branch first.
- Branch naming:
feature/<short-description>fix/<short-description>refactor/<short-description>chore/<short-description>
- Keep branches short-lived and merge back quickly.
Merge and Safety
- Rebase or sync frequently with the base branch to reduce drift.
- Resolve conflicts carefully and re-run verification before merge.
- Never force-push shared branches unless explicitly requested.
- Never commit
.env, secrets, build artifacts, or unrelated generated files.
Scope Discipline
- Commit only files related to the current task.
- If unrelated local changes exist, avoid mixing them into the same commit.
- In change summaries, clearly 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.
- 2d 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 (3 stars, last pushed 3d ago), licensed MIT. It adds 384 tokens to every session, about $0.0019 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
cursorrules
Mój ulubiony kolor to bordowy.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.