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-prep-release)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/git-prep-release"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/git-prep-release/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-prep-release"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/git-prep-release.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.03583 |
| Opus 5.5 | $0.00000 | $0.01433 |
| Sonnet 5.5 | $0.00000 | $0.00717 |
| Haiku 4.5 | $0.00000 | $0.00358 |
Grade A, and why
git-prep-release 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 — 557 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Preparation and Version Management Guide
This prompt provides systematic release preparation including version management, testing coordination, documentation updates, and deployment planning.
🎯 RELEASE PREPARATION OBJECTIVES:
- PLAN release scope and validate feature completeness
- MANAGE version numbers following semantic versioning
- GENERATE comprehensive changelog with all changes documented
- COORDINATE testing across all environments and stakeholders
- PREPARE deployment with rollback plans and monitoring
📋 RELEASE PLANNING AND SCOPE DEFINITION:
STEP 1: Release Type and Scope Assessment
Release Type Classification:
## Release Classification
**MAJOR RELEASE (X.0.0):**
- [ ] Breaking API changes
- [ ] Major architectural changes
- [ ] Significant UI/UX overhaul
- [ ] New platform/technology adoption
- [ ] Removal of deprecated features
**MINOR RELEASE (X.Y.0):**
- [ ] New features added
- [ ] Enhanced functionality
- [ ] Performance improvements
- [ ] Non-breaking API additions
- [ ] New integrations
**PATCH RELEASE (X.Y.Z):**
- [ ] Bug fixes only
- [ ] Security patches
- [ ] Documentation updates
- [ ] Configuration improvements
- [ ] No new features
Release Scope Documentation:
## Release [VERSION] Scope
### Release Type: [MAJOR/MINOR/PATCH]
### Target Date: [Release date]
### Release Manager: [Name]
### Features Included:
- [ ] [Feature 1]: [Status, Testing status]
- [ ] [Feature 2]: [Status, Testing status]
- [ ] [Feature 3]: [Status, Testing status]
### Bug Fixes Included:
- [ ] [Issue 1]: [Description, PR link]
- [ ] [Issue 2]: [Description, PR link]
- [ ] [Issue 3]: [Description, PR link]
### Breaking Changes:
- [ ] [Change 1]: [Impact, Migration guide]
- [ ] [Change 2]: [Impact, Migration guide]
### Dependencies Updated:
- [ ] [Package 1]: [Old version → New version]
- [ ] [Package 2]: [Old version → New version]
### Migration Requirements:
- [ ] Database migrations: [List any required migrations]
- [ ] Configuration changes: [Environment variables, etc.]
- [ ] API client updates: [Required client changes]
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 · 557 lines · 0 tokens per session scan A 94b71532dd15
git-prep-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,583 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
changesets
Changeset format and bump rules enforced by CI.
release-policy
Release, versioning, and signing policy for setmac.
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-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.
release-checklist
What to update with each code change or version release.
github-cli-guide
A guide on how to use the Github CLI (gh cli) especially related to creating issues via the CLI.