always-push-pr

A repository rule requiring completed work to be committed to a feature branch, pushed to the remote repository, and kept in a pull request for review.

In plain words
What is it for?
Use it in projects where code changes must follow a commit, push, and pull-request workflow.
Why use it?
It prevents finished changes from remaining only on one computer and keeps them ready for review without merging them automatically.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/itsmemeworks/adhx/always-push-pr
Clone the repo
git clone --depth 1 https://github.com/itsmemeworks/adhx

Made for: Cursor.

Per session 211 This file is loaded in full into every session.
When invoked 211 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00211 $0.00211
Opus 5 $0.00105 $0.00105
Sonnet 5 $0.00042 $0.00042
Haiku 4.5 $0.00021 $0.00021

Measured yesterday against content hash 16093618e40c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

always-push-pr 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.

.cursor/rules/always-push-pr.mdc · 18 lines

What it actually says

Git: always push, always keep a PR

This repo overrides any global “don't commit / don't push / don't open a PR unless asked” preference.

After substantive work (feature, fix, docs, workflow):

  1. Commit on a feature branch — never to main. Conventional Commits, lowercase subject.
  2. Push to origin (git push -u origin HEAD for a new branch). No force-push unless the user asks.
  3. Open or update a PR with gh, using the account named in gitignored CLAUDE.local.md. If a PR already exists for the branch, push updates it — do not open a duplicate. If none exists, gh pr create.
  4. Do not merge. The user merges PRs manually.

Skip only when the user explicitly says the work is local-only / do not share.

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.

  1. yesterday First seen · 18 lines · 211 tokens per session scan A 16093618e40c

Subscribe to this mod's changes

always-push-pr is a cursor rule published in the GitHub repository itsmemeworks/adhx (15 stars, last pushed 4d ago), licensed MIT. It adds 211 tokens to every session, about $0.0011 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.