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/newfront/pyspark-datagenWrote 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/newfront/pyspark-datagen/git-branching)<a href="https://agentmods.dev/rules/newfront/pyspark-datagen/git-branching"><img src="https://agentmods.dev/badge/rules/newfront/pyspark-datagen/git-branching/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/newfront/pyspark-datagen/git-branching"><img src="https://agentmods.dev/badge/rules/newfront/pyspark-datagen/git-branching.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.00314 | $0.00314 |
| Opus 5.5 | $0.00126 | $0.00126 |
| Sonnet 5.5 | $0.00063 | $0.00063 |
| Haiku 4.5 | $0.00031 | $0.00031 |
Grade A, and why
git-branching 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
Branching Workflow
Before Starting Any Work
- Check the current branch. If on
main, create and switch to a new branch before making any changes. - Suggest a branch name using the pattern
feat/<short-description>(e.g.feat/add-lineage-api). - Always offer the user a choice: present the suggested name and an option to enter their own.
Use the AskQuestion tool to let the user pick:
- Option A: the suggested
feat/*name - Option B: "I'll provide my own branch name"
Branch Naming Conventions
| Prefix | Use when |
|---|---|
feat/ |
Adding new functionality |
fix/ |
Fixing a bug |
chore/ |
Build, CI, dependency, or repo upkeep |
refactor/ |
Restructuring without behavior change |
test/ |
Adding or improving tests only |
Keep names short, lowercase, and hyphen-separated (e.g. feat/column-lineage-parser).
Rules
- Never commit directly to
main. - Create the branch with
git checkout -b <branch>before the first file change. - One logical unit of work per branch.
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 · 37 lines · 314 tokens per session scan A 8dbe21bbe3ad
git-branching is a cursor rule published in the GitHub repository newfront/pyspark-datagen (5 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 314 tokens to every session, about $0.0013 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
rebase-only-merged-agents
When rebasing after a merge, only rebase the agents whose branches you just merged. Do not rebase agents that are still running.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
git-workflow
Rules for git operations, commit strategy, and GitHub CLI usage.
release-checklist
What to update with each code change or version release.
git-workflow
Git commit format and PR process - conventional commits.
branching-merging-strategy
This is a set of instructions to the AI Assistant for branching and merging strategy.