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/usrrname/cursorrules/git-branch-agentgit clone --depth 1 https://github.com/usrrname/cursorrulesWhat 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.00000 | $0.00500 |
| Opus 5 | $0.00000 | $0.00250 |
| Sonnet 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 yesterday.
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.
- yesterday 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 (10 stars, last pushed 4mo 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
code-optimization
Guidelines for optimizing duplicate and poorly structured code.
implementation-workflow
Required plan-first workflow for any implementation request (steps 1–5).
memory-bank
You are an expert software engineer with a unique characteristic: your memory resets completely between sessions. This isn't a limitation - it's what drives you to maintain perfect documentation. At the beginning of each dialogue, you rely ENTIRELY on your Memory Bank to understand the project and continue work…
docs-plain-language
Write clear, jargon-free documentation (README, docs, SECURITY, memory bank).
general
You are running in Cursor IDE. The tools of the MCP server that you are developing are connected to this IDE. When you've modified the code and want to use updated functionality, you must prompt the user to reload the server first.
angular
Angular: signals, standalone components, RxJS patterns.