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/oakensoul/nextjs-cursor-promptsWrote 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/oakensoul/nextjs-cursor-prompts/git-branch-create)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/git-branch-create"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/git-branch-create/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/oakensoul/nextjs-cursor-prompts/git-branch-create"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/git-branch-create.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.02863 |
| Opus 5.5 | $0.00000 | $0.01145 |
| Sonnet 5.5 | $0.00000 | $0.00573 |
| Haiku 4.5 | $0.00000 | $0.00286 |
Grade A, and why
git-branch-create 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.
How it starts
The opening of the file, as written. The whole thing — 473 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Branch Creation Guide
This prompt handles systematic branch creation following Git workflow standards, ensuring proper naming conventions, base branch selection, and documentation setup.
🎯 BRANCH CREATION OBJECTIVES:
- DETERMINE branch type and apply appropriate naming conventions
- SELECT correct base branch based on workflow standards
- CREATE branch with proper setup and initial configuration
- ESTABLISH tracking and team communication
- PREPARE development environment for the new branch
📋 BRANCH CREATION PROCESS:
STEP 1: Branch Type and Naming Analysis
Branch Type Classification:
## Branch Type Assessment
**FEATURE BRANCH:**
- [ ] New functionality or enhancement
- [ ] User-facing feature development
- [ ] API endpoint creation
- [ ] UI/UX improvements
- Naming: `feature/[description]`
**BUGFIX BRANCH:**
- [ ] Non-critical bug resolution
- [ ] Issue tracking integration
- [ ] Performance improvements
- [ ] Code quality fixes
- Naming: `bugfix/[issue-id]-[description]`
**EXPERIMENTAL BRANCH:**
- [ ] Proof of concept work
- [ ] Technology evaluation
- [ ] Architecture exploration
- [ ] Research and development
- Naming: `experiment/[description]`
**DOCUMENTATION BRANCH:**
- [ ] Documentation updates
- [ ] README improvements
- [ ] API documentation
- [ ] User guides and tutorials
- Naming: `docs/[description]`
**REFACTOR BRANCH:**
- [ ] Code restructuring
- [ ] Performance optimization
- [ ] Technical debt reduction
- [ ] Architecture improvements
- Naming: `refactor/[description]`
Branch Naming Validation:
# Validate branch name against conventions
BRANCH_NAME="[proposed-name]"
# Check naming patterns
case $BRANCH_NAME in
feature/*|bugfix/*|docs/*|refactor/*|experiment/*)
echo "✅ Valid branch name format"
;;
*)
echo "❌ Invalid branch name format"
echo "Use: feature/*, bugfix/*, docs/*, refactor/*, experiment/*"
exit 1
;;
esac
# Check for proper description format
if [[ $BRANCH_NAME =~ ^[a-z]+/[a-z0-9-]+$ ]]; then
echo "✅ Valid naming convention"
else
echo "❌ Use lowercase, hyphens only, no spaces or special characters"
exit 1
fi
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 · 473 lines · 0 tokens per session scan A ebe19be1bf46
git-branch-create is a cursor rule published in the GitHub repository oakensoul/nextjs-cursor-prompts (4 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,863 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
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.
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.
git-workflow
Rules for git operations, commit strategy, and GitHub CLI usage.
release-checklist
What to update with each code change or version release.
branching-merging-strategy
This is a set of instructions to the AI Assistant for branching and merging strategy.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.