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/dasomel/oh-my-cursorWrote 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/dasomel/oh-my-cursor/git-workflow)<a href="https://agentmods.dev/rules/dasomel/oh-my-cursor/git-workflow"><img src="https://agentmods.dev/badge/rules/dasomel/oh-my-cursor/git-workflow/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/dasomel/oh-my-cursor/git-workflow"><img src="https://agentmods.dev/badge/rules/dasomel/oh-my-cursor/git-workflow.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.00000 | $0.00348 |
| Opus 5.5 | $0.00000 | $0.00139 |
| Sonnet 5.5 | $0.00000 | $0.00070 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
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 2mo 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 Standards
Commit Messages (Conventional Commits)
Format: <type>(<scope>): <description>
Types:
feat: New featurefix: Bug fixdocs: Documentation onlyrefactor: Code change without feature/fixtest: Adding/fixing testschore: Build, config, dependenciesperf: Performance improvement
Examples:
feat(auth): add OAuth2 Google login
fix(api): handle null response from user service
test(parser): add edge cases for empty input
chore(deps): upgrade typescript to 5.7
Rules:
- Lowercase, no period at end
- Max 72 chars in first line
- Imperative mood: "add" not "added"
- Reference issues:
fix(auth): handle session expiry (#142)
Branch Strategy
main ← production-ready
develop ← integration branch
feat/name ← new features
fix/issue-123 ← bug fixes
chore/name ← maintenance
Pull Request Rules
- One PR per feature/fix
- Link to issue:
Closes #123 - Self-review before requesting review
- All tests passing before review request
- No force-push to shared branches
Anti-Patterns
git commit -m "fix stuff"— meaningless messages- Giant PRs (>500 lines changed)
- Committing generated files
- Force-pushing to main/develop
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.
- 2mo ago First seen · 59 lines · 0 tokens per session scan A 1d9a5a1ebbe6
git-workflow is a cursor rule published in the GitHub repository dasomel/oh-my-cursor (3 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 348 tokens. 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 workflow — commit format, push policy, and PR process.
commits
Conventional Commits standards for clear, semantic commit messages.
no-ai-contributors
Never add AI tools as git authors or project contributors.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.
git-discipline
Commit, push, and branching rules. Owns ALL git behavior; other files state only their deviations.
git-commit-standards
Enforce structured Git commit messages.