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/usrrname/cursorrulesWrote 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/usrrname/cursorrules/release-package-version-auto)<a href="https://agentmods.dev/rules/usrrname/cursorrules/release-package-version-auto"><img src="https://agentmods.dev/badge/rules/usrrname/cursorrules/release-package-version-auto/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/usrrname/cursorrules/release-package-version-auto"><img src="https://agentmods.dev/badge/rules/usrrname/cursorrules/release-package-version-auto.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.01414 |
| Opus 5.5 | $0.00000 | $0.00566 |
| Sonnet 5.5 | $0.00000 | $0.00283 |
| Haiku 4.5 | $0.00000 | $0.00141 |
Grade A, and why
release-package-version-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 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Package Version Management
Critical Rules
- Must offer to update package.json version automatically
- Must calculate new version based on semantic versioning
- Must handle custom version inputs
- Must offer to commit version changes
- Must offer to push version commits
- Must provide clear feedback about version update status
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: |
🔄 Package Version Management Process
I'll help you update the version in package.json and manage the version commit.
- Offer Version Bump Update:
echo "" echo "🔄 Would you like me to automatically update the version in package.json?" echo "Current version: $CURRENT_VERSION" # Calculate new version based on user choice if [ "$VERSION_BUMP" == "major" ]; then NEW_VERSION=$(echo $CURRENT_VERSION | awk -F. '{print $1+1 ".0.0"}') elif [ "$VERSION_BUMP" == "minor" ]; then NEW_VERSION=$(echo $CURRENT_VERSION | awk -F. '{print $1 "." $2+1 ".0"}') elif [ "$VERSION_BUMP" == "patch" ]; then NEW_VERSION=$(echo $CURRENT_VERSION | awk -F. '{print $1 "." $2 "." $3+1}') elif [ "$VERSION_BUMP" == "custom" ]; then NEW_VERSION="$CUSTOM_VERSION" fi echo "New version would be: $NEW_VERSION" read -p "Update package.json version? (y/N): " UPDATE_VERSION if [[ "$UPDATE_VERSION" =~ ^[Yy]$ ]]; then echo "🔄 Updating package.json version..." # Update package.json version using npm if [ "$VERSION_BUMP" == "custom" ]; then # For custom version, we need to manually update node -e " const fs = require('fs'); const pkg = JSON.parse(fs.readFileSync('package.json', 'utf8')); pkg.version = '$NEW_VERSION'; fs.writeFileSync('package.json', JSON.stringify(pkg, null, 2) + '\n'); console.log('✅ Updated package.json version to $NEW_VERSION'); " else # Use npm version for standard bumps npm version $VERSION_BUMP --no-git-tag echo "✅ Updated package.json version to $NEW_VERSION" fi # Offer to commit the version change echo "" echo "🔄 Would you like me to commit the version change?" read -p "Commit version bump? (y/N): " COMMIT_VERSION if [[ "$COMMIT_VERSION" =~ ^[Yy]$ ]]; then echo "🔄 Committing version change..." git add package.json git commit -m "chore: bump version to $NEW_VERSION" echo "✅ Version change committed successfully" # Offer to push the commit echo "" echo "🔄 Would you like me to push the version commit?" read -p "Push version commit? (y/N): " PUSH_VERSION if [[ "$PUSH_VERSION" =~ ^[Yy]$ ]]; then echo "🔄 Pushing version commit..." git push origin $CURRENT_BRANCH echo "✅ Version commit pushed successfully" fi fi else echo "⏭️ Skipping version update" fi
- Offer Version Bump Update:
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 · 167 lines · 0 tokens per session scan A f2ca6d6efcfb
release-package-version-auto is a cursor rule published in the GitHub repository usrrname/cursorrules (11 stars, last pushed 6mo ago), licensed ISC. It costs nothing until one of its globs matches a file; then it loads 1,414 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
git-workflow
Git workflow: commits, branches, PRs, history management.
git-master
Git operations — clean commits, PR prep, conflict resolution, change summaries.
release
Changesets release pipeline - version PR and its dispatched CI check, shared vX.Y.Z tag, CI gate before tagging, release:check gate, Dependabot changesets, no npm publish, GITHUBTOKEN tag trigger limitation.
changesets
Writing changesets - when one is needed, apps-only frontmatter, bump levels for deployed apps, summary style, non-interactive creation.
cd
GitHub Actions CD - called by release.yml after the tag, no push-tags trigger, cf workers versions create then a 100% deployment in deployOrder, scoped API token on the production environment, GitHub-owned deployment record.
changeset
Guidelines for using Changesets (npm run changeset) to manage versioning and changelogs.