Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/oakensoul/nextjs-cursor-promptsnpx agentmods add rules/oakensoul/nextjs-cursor-prompts/git-branch-releaseWrote 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-release)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/git-branch-release"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/git-branch-release.svg" alt="Measured on agentmods" 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.03360 |
| Opus 5 | $0.00000 | $0.01680 |
| Sonnet 5 | $0.00000 | $0.00672 |
| Haiku 4.5 | $0.00000 | $0.00336 |
Grade A, and why
git-branch-release scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -f https://myapp.com/health || { How it starts
The opening of the file, as written. The whole thing — 512 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Release Branch Execution Guide
This prompt handles the execution phase of release workflow - creating release branches, finalizing versions, executing deployments, and managing the complete release lifecycle.
🎯 RELEASE EXECUTION OBJECTIVES:
- EXECUTE release branch creation from prepared release plan
- FINALIZE version numbers and apply tags properly
- MERGE release branches to main and develop following workflow
- DEPLOY to production with proper validation and monitoring
- COMPLETE release lifecycle with documentation and cleanup
📋 RELEASE EXECUTION PROCESS:
STEP 1: Pre-execution Validation
Release Readiness Verification:
# Verify release preparation completed
echo "Validating release readiness..."
# Check that release plan exists
if [ ! -f "docs/releases/release-v[VERSION]-plan.md" ]; then
echo "❌ Release plan not found. Run git-prep-release.mdc first"
exit 1
fi
# Verify develop branch is ready
git checkout develop
git pull origin develop
# Confirm all planned features are merged
git log --oneline --since="1 month ago" | grep -E "(feat|fix|docs):"
# Check CI/CD status
echo "✅ Develop branch ready for release"
Environment and Dependencies Check:
# Verify all dependencies are secure and up to date
npm audit # Security audit
npm outdated # Check for outdated packages
# Run comprehensive test suite
npm run test:full # All tests including integration
npm run test:e2e # End-to-end tests
npm run test:accessibility # A11y compliance tests
# Verify build process
npm run build # Production build
npm run build:analysis # Bundle analysis
echo "✅ All quality gates passed"
STEP 2: Release Branch Creation and Configuration
Release Branch Creation:
# Set release variables
RELEASE_VERSION="[VERSION]" # e.g., "1.2.0"
RELEASE_BRANCH="release/v$RELEASE_VERSION"
CURRENT_DATE=$(date +%Y-%m-%d)
echo "Creating release branch: $RELEASE_BRANCH"
# Create release branch from develop
git checkout develop
git pull origin develop
git checkout -b $RELEASE_BRANCH
# Push release branch to remote
git push -u origin $RELEASE_BRANCH
echo "✅ Release branch $RELEASE_BRANCH created"
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.
- 6d ago First seen · 512 lines · 0 tokens per session scan A 356d75fb11d6
git-branch-release 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 3,360 tokens. A static security scan graded it A with 1 finding (makes network calls). 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
monorepo-versioning
Internal peerDependency ranges and Changesets conventions for the SDK monorepo — avoid major-version cascades.
release-notes
Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.
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.
release-checklist
What to update with each code change or version release.
release-policy
Release, versioning, and signing policy for setmac.
bump-project-version
The user can provide version in one of three ways.