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-code-shipit)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/git-code-shipit"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/git-code-shipit/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-code-shipit"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/git-code-shipit.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.03021 |
| Opus 5.5 | $0.00000 | $0.01208 |
| Sonnet 5.5 | $0.00000 | $0.00604 |
| Haiku 4.5 | $0.00000 | $0.00302 |
Grade A, and why
git-code-shipit 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.
How it starts
The opening of the file, as written. The whole thing — 362 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Code Ship It - Complete Workflow Orchestrator
🚢 This is the ultimate "Ship It" command - a comprehensive git workflow that takes you from code changes to GitHub push with complete quality validation and documentation.
🎯 SHIP IT OBJECTIVES:
- ORCHESTRATE complete git workflow from preparation through push
- ENSURE comprehensive quality at every phase with zero tolerance for failures
- PROVIDE detailed reporting of all operations and validations
- MAINTAIN safety checkpoints with clear go/no-go decisions
- DELIVER production-ready code to GitHub with confidence
🚢 SHIP IT WORKFLOW PHASES:
Phase 1: PREPARATION → Analyze, document, plan
Phase 2: COMMIT → Validate, execute, verify
Phase 3: PUSH → Quality gates, security, deploy
Phase 4: CONFIRMATION → Success report, monitoring
📋 COMPLETE SHIPIT PROCESS:
🔍 PHASE 1: PREPARATION
Following .cursor/prompts/git/git-code-prep.mdc
Comprehensive Change Analysis:
- Analyze all modifications - Files changed, features added, bugs fixed
- Determine commit strategy - Single vs. multiple commits, logical grouping
- Update documentation - Changelog, README, API docs, sitemap
- Plan commit messages - Conventional commit format preparation
- Execute initial quality checks - Precommit hooks, linting, type checking
Phase 1 Success Criteria:
- Change analysis complete - Full understanding of modifications
- Documentation updated - Changelog, LLMs.mdc, sitemap current
- Commit strategy planned - Clear execution plan prepared
- Initial quality gates pass - Precommit hooks successful
- Files staged appropriately - Correct staging for planned commits
🚨 Phase 1 Checkpoint:
CONTINUE TO PHASE 2? [GO/NO-GO]
- If NO-GO: Stop, address preparation issues, re-run Phase 1
✅ PHASE 2: COMMIT EXECUTION
Following .cursor/prompts/git/git-code-commit.mdc
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 · 362 lines · 0 tokens per session scan A a48aa765e2f6
git-code-shipit 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,021 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
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.