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.
npx agentmods add rules/usrrname/cursorrules/release-git-tags-autogit clone --depth 1 https://github.com/usrrname/cursorrulesWhat 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 | $0.00000 | $0.02026 |
| Opus 5 | $0.00000 | $0.01013 |
| Sonnet 5 | $0.00000 | $0.00405 |
| Haiku 4.5 | $0.00000 | $0.00203 |
Grade A, and why
release-git-tags-auto 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 yesterday.
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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Git Tag Management
Critical Rules
- Must check for existing tags before creating new ones
- Must handle local and remote tag conflicts gracefully
- Must provide multiple resolution options for tag conflicts
- Must validate tag format and naming conventions
- Must offer to push tags to remote repository
- Must provide clear error messages and resolution steps
filters:
- type: content pattern: "(release|version|tag|bump|publish|deploy).*(create|make|generate|prepare|ready)"
- type: git_branch pattern: "^(?!main$|master$).*$"
- type: event pattern: "chat_start|chat_response"
actions:
-
type: generate content: |
🏷️ Git Tag Management Process
I'll help you create and manage git tags for your release.
- Offer Git Tag Creation:
echo "🏷️ Would you like me to create a git tag for version $NEW_VERSION?" echo "This will create a tag that marks this exact point in your release." read -p "Create git tag v$NEW_VERSION? (y/N): " CREATE_TAG if [[ "$CREATE_TAG" =~ ^[Yy]$ ]]; then echo "🔄 Creating git tag v$NEW_VERSION..." # Check if tag already exists if git tag -l "v$NEW_VERSION" | grep -q "v$NEW_VERSION"; then echo "❌ ERROR: Git tag v$NEW_VERSION already exists!" echo "" echo "Existing tag details:" git show --no-patch --format="%H%n%an%n%ad%n%s" "v$NEW_VERSION" 2>/dev/null || echo "Tag exists but details unavailable" echo "" echo "Options:" echo "1. Use a different version number" echo "2. Delete the existing tag (if you're sure it's safe)" echo "3. Skip tag creation and create it manually later" echo "" read -p "Choose option (1-3): " TAG_CONFLICT_CHOICE case $TAG_CONFLICT_CHOICE in 1) echo "Please restart the release workflow with a different version number" echo "❌ Release workflow terminated due to tag conflict" exit 1 ;; 2) echo "⚠️ WARNING: You're about to delete an existing tag!" echo "This action cannot be undone and may affect other developers." read -p "Are you absolutely sure? Type 'DELETE' to confirm: " DELETE_CONFIRM if [[ "$DELETE_CONFIRM" == "DELETE" ]]; then echo "🔄 Deleting existing tag v$NEW_VERSION..." git tag -d "v$NEW_VERSION" # Also delete from remote if it exists there if git ls-remote --tags origin "v$NEW_VERSION" | grep -q "v$NEW_VERSION"; then echo "🔄 Deleting remote tag v$NEW_VERSION..." git push origin ":refs/tags/v$NEW_VERSION" fi echo "✅ Existing tag deleted successfully" else echo "❌ Tag deletion cancelled. Release workflow terminated" exit 1 fi ;; 3) echo "⏭️ Skipping tag creation due to conflict" CREATE_TAG="" ;; *) echo "❌ Invalid choice. Release workflow terminated" exit 1 ;; esac fi # Create the git tag (only if we didn't skip due to conflict) if [[ "$CREATE_TAG" =~ ^[Yy]$ ]]; then git tag v$NEW_VERSION echo "✅ Git tag v$NEW_VERSION created successfully" # Offer to push the tag echo "" echo "🔄 Would you like me to push the git tag to the remote repository?" echo "This makes the tag available to other developers and CI/CD systems." read -p "Push git tag v$NEW_VERSION? (y/N): " PUSH_TAG if [[ "$PUSH_TAG" =~ ^[Yy]$ ]]; then echo "🔄 Pushing git tag v$NEW_VERSION..." # Check for remote tag conflicts before pushing if git ls-remote --tags origin "v$NEW_VERSION" | grep -q "v$NEW_VERSION"; then echo "❌ ERROR: Remote tag v$NEW_VERSION already exists!" echo "The local tag was created, but cannot be pushed due to remote conflict." echo "" echo "Options:" echo "1. Delete the remote tag first (requires appropriate permissions)" echo "2. Keep the local tag only" echo "3. Delete the local tag and skip" echo "" read -p "Choose option (1-3): " REMOTE_CONFLICT_CHOICE case $REMOTE_CONFLICT_CHOICE in 1) echo "🔄 Deleting remote tag v$NEW_VERSION..." git push origin ":refs/tags/v$NEW_VERSION" echo "🔄 Now pushing local tag..." git push origin v$NEW_VERSION echo "✅ Git tag v$NEW_VERSION pushed successfully" ;; 2) echo "⏭️ Keeping local tag only. You can push it later with: git push origin v$NEW_VERSION" ;; 3) echo "🔄 Deleting local tag..." git tag -d "v$NEW_VERSION" echo "⏭️ Tag creation cancelled" ;; *) echo "❌ Invalid choice. Keeping local tag only" ;; esac else git push origin v$NEW_VERSION echo "✅ Git tag v$NEW_VERSION pushed successfully" echo "" echo "🎉 Release tag is now live!" echo "Tag URL: https://github.com/[USERNAME]/[REPO]/releases/tag/v$NEW_VERSION" fi else echo "⏭️ Tag created locally but not pushed" echo "You can push it later with: git push origin v$NEW_VERSION" fi fi else echo "⏭️ Skipping git tag creation" echo "You can create the tag manually later with: git tag v$NEW_VERSION" fi
- Offer Git Tag Creation:
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.
- yesterday First seen · 233 lines · 0 tokens per session scan A c3f2ca18a1d8
release-git-tags-auto is a cursor rule published in the GitHub repository usrrname/cursorrules (10 stars, last pushed 4mo ago), licensed ISC. It costs nothing until one of its globs matches a file; then it loads 2,026 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
code-optimization
Guidelines for optimizing duplicate and poorly structured code.
implementation-workflow
Required plan-first workflow for any implementation request (steps 1–5).
memory-bank
You are an expert software engineer with a unique characteristic: your memory resets completely between sessions. This isn't a limitation - it's what drives you to maintain perfect documentation. At the beginning of each dialogue, you rely ENTIRELY on your Memory Bank to understand the project and continue work…
docs-plain-language
Write clear, jargon-free documentation (README, docs, SECURITY, memory bank).
general
You are running in Cursor IDE. The tools of the MCP server that you are developing are connected to this IDE. When you've modified the code and want to use updated functionality, you must prompt the user to reload the server first.
angular
Angular: signals, standalone components, RxJS patterns.