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/usrrname/cursorrulesWrote 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/usrrname/cursorrules/git-branch-agent)<a href="https://agentmods.dev/rules/usrrname/cursorrules/git-branch-agent"><img src="https://agentmods.dev/badge/rules/usrrname/cursorrules/git-branch-agent/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/usrrname/cursorrules/git-branch-agent"><img src="https://agentmods.dev/badge/rules/usrrname/cursorrules/git-branch-agent.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.00500 |
| Opus 5.5 | $0.00000 | $0.00200 |
| Sonnet 5.5 | $0.00000 | $0.00100 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
git-branch-agent 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
Critical Rules
- Always
git statusfirst; stash/commit before switching - Branch names:
<type>/<ticket?>-kebab-description - Allowed types: feature, fix, hotfix, release, docs, refactor, test, chore, experiment, spike
- Start new work from updated
main - Delete only merged branches (never current branch)
git fetch --allbefore new branches
Naming Examples
feature/#123-user-auth
fix/#345-login-timeout
refs/docs-api
filters:
- type: event pattern: "(pre_checkout|post_checkout|branch_create|branch_delete)"
- type: content pattern: "(checkout|branch|gco|gcb)"
matches: | git checkout $branch git branch $branch git branch -d $branch gco $branch gcb $branch
transforms: |
{{
const op = context.getOperation();
const branch = context.getBranchName();
if (!/^([a-z]+)/(#?\d+-)?[a-z0-9-]+$/.test(branch)) return suggestValidBranchName(branch);
if (op === 'checkout') return git status && ${command};
if (op === 'delete') return git branch --merged | grep ${branch} && ${command};
return command;
}}
examples:
- input: "git checkout feature" output: "git status && git checkout feature/#123-descriptive"
- input: "git branch -d old" output: "git branch --merged | grep old && git branch -d feature/old"
tests:
- input: "gco main" output: "git status && git checkout main"
metadata: priority: high
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 First seen · 65 lines · 500 tokens per session scan A d518913cf959
git-branch-agent is a cursor rule published in the GitHub repository usrrname/cursorrules (11 stars, last pushed 6mo ago), licensed ISC. It costs nothing until one of its globs matches a file; then it loads 500 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-workflow
Git workflow: commits, branches, PRs, history management.
git-master
Git operations — clean commits, PR prep, conflict resolution, change summaries.
git-conventional-commit-messages
Cursor rules for Git development with conventional commit messages integration.
github-cursorrules-prompt-file-instructions
Cursor rules for GitHub development with instructions integration.
python-github-setup-cursorrules-prompt-file
Cursor rules for Python development with GitHub setup integration.
gitflow
Gitflow Workflow Rules. These rules should be applied when performing git operations.