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-create-hotfix)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/git-create-hotfix"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/git-create-hotfix/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-create-hotfix"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/git-create-hotfix.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.03587 |
| Opus 5.5 | $0.00000 | $0.01435 |
| Sonnet 5.5 | $0.00000 | $0.00717 |
| Haiku 4.5 | $0.00000 | $0.00359 |
Grade A, and why
git-create-hotfix 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 — 487 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hotfix Environment Setup and Branch Creation
This prompt automates hotfix environment setup from a specific commit hash, creates proper branching, PR, and documentation for critical production issues.
🎯 HOTFIX SETUP OBJECTIVES:
- STAGE current environment safely and preserve work-in-progress
- CREATE hotfix branch from specified commit hash
- GENERATE documentation and issue tracking automatically
- CREATE pull request with proper templates and requirements
- CONFIGURE environment for hotfix development workflow
📋 REQUIRED INPUTS:
Commit Hash Input:
**REQUIRED**: Provide the specific commit hash to create the hotfix from:
**Target Commit Hash**: [COMMIT_HASH]
**Commit Message**: [Brief description of the target commit]
**Commit Date**: [When this commit was made]
**Reason for Selection**: [Why this specific commit for the hotfix]
Hotfix Details:
**Issue ID**: [PROD-123, SEC-456, etc.]
**Severity**: [CRITICAL/HIGH/MEDIUM]
**Brief Description**: [payment-timeout, auth-bypass, etc.]
**Estimated Complexity**: [SIMPLE/MEDIUM/COMPLEX]
**Business Impact**: [Revenue/Security/User Experience]
🛠️ AUTOMATED ENVIRONMENT SETUP:
STEP 1: Environment Staging and Preservation
Current Work Preservation:
# Check current git status and stage everything safely
echo "🔍 Checking current git status..."
git status --porcelain
# Stash any uncommitted work with descriptive message
echo "💾 Preserving current work..."
TIMESTAMP=$(date +"%Y%m%d_%H%M%S")
git stash push -m "PRE_HOTFIX_WORK_${TIMESTAMP}_$(git rev-parse --short HEAD)"
# Record stash information for later restoration
STASH_REF=$(git stash list | head -n 1 | cut -d: -f1)
echo "📝 Work stashed as: $STASH_REF"
# Create restoration script
cat > .hotfix_restoration.sh << EOF
#!/bin/bash
# Hotfix restoration script - generated $(date)
echo "Restoring pre-hotfix work..."
git stash pop $STASH_REF
rm .hotfix_restoration.sh
echo "✅ Pre-hotfix work restored"
EOF
chmod +x .hotfix_restoration.sh
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 · 487 lines · 0 tokens per session scan A 7faa5da946e3
git-create-hotfix 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,587 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.