What is gitflow-release-cleanup?

A release rule for GitFlow repositories, a branching model where release and emergency-fix branches are merged into the main development branches.

Use it after a release or hotfix is merged into master, tagged, and merged back into develop, to delete the completed branch locally and on origin.

It prevents finished release and hotfix branches from remaining on the remote repository after their changes have been merged and tagged.

gitflow-release-cleanup — Cursor rule for Cursor by olibartfast

Install

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.

Clone the repo

git clone --depth 1 https://github.com/olibartfast/neuriplo-infer

Made for: Cursor.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/olibartfast/neuriplo-infer/gitflow-release-cleanup.svg)](https://agentmods.dev/rules/olibartfast/neuriplo-infer/gitflow-release-cleanup)

Your own site

<a href="https://agentmods.dev/rules/olibartfast/neuriplo-infer/gitflow-release-cleanup"><img src="https://agentmods.dev/badge/rules/olibartfast/neuriplo-infer/gitflow-release-cleanup.svg" alt="Measured on agentmods" height="20"></a>

Per session 453 This file is loaded in full into every session.

When invoked 453 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00453	$0.00453
Opus 5	$0.00227	$0.00227
Sonnet 5	$0.00091	$0.00091
Haiku 4.5	$0.00045	$0.00045

Measured 8d ago against content hash 59627ecdfce9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

gitflow-release-cleanup 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 8d 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.

.cursor/rules/gitflow-release-cleanup.mdc · 45 lines

What it actually says

GitFlow release and hotfix branch cleanup

Applies to coding repos listed in ops/policies.yaml (neuriplo-tasks, neuriplo, neuriplo-infer, neuriplo-kserve-client, neuriplo-kserve-runtime, videocapture). Not required for neuriplo-platform.

After a release or hotfix is finished

When release/* or hotfix/* has been merged to master (tagged) and back-merged to develop, delete the topic branch locally and on origin. Do not leave finished release/hotfix branches on the remote.

# Example: release/0.7.0 completed on master + develop
git checkout develop
git branch -d release/0.7.0
git push origin --delete release/0.7.0

Same for hotfix/* after merge to master and develop.

Do not

Push release/* or hotfix/* to origin and leave them there after the release is complete.
Use a lingering remote release branch as the record of a shipped version — the master tag (vX.Y.Z) is the immutable release ref.
Push release/* only to watch CI when develop CI covers the same commits; prefer waiting on develop/master workflow results unless the user asks to push the release branch for a PR.

Agent checklist (release complete)

Merge release/X.Y.Z → master; tag vX.Y.Z; push master and tag.
Merge release/X.Y.Z → develop; bump dev VERSION if the repo does that; push develop.
git branch -d release/X.Y.Z
git push origin --delete release/X.Y.Z
Confirm: git branch -a | grep release shows no finished release branch.

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.

8d ago First seen · 45 lines · 453 tokens per session scan A 59627ecdfce9

Subscribe to this mod's changes

gitflow-release-cleanup is a cursor rule published in the GitHub repository olibartfast/neuriplo-infer (103 stars, last pushed 2d ago), licensed MIT. It adds 453 tokens to every session, about $0.0023 per session on Opus 5. 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-30.

Git and workflow Releases deim dfine object-detection rf-detr rt-detr yolo

monorepo-versioning

Internal peerDependency ranges and Changesets conventions for the SDK monorepo — avoid major-version cascades.

solvapay/solvapay-sdk · 0 tokens

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.

thatrebeccarae/claude-marketing · 50 tokens

gitflow-release-cleanup