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/itsmemeworks/adhxWrote 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/itsmemeworks/adhx/always-push-pr)<a href="https://agentmods.dev/rules/itsmemeworks/adhx/always-push-pr"><img src="https://agentmods.dev/badge/rules/itsmemeworks/adhx/always-push-pr/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/itsmemeworks/adhx/always-push-pr"><img src="https://agentmods.dev/badge/rules/itsmemeworks/adhx/always-push-pr.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.00279 | $0.00279 |
| Opus 5.5 | $0.00112 | $0.00112 |
| Sonnet 5.5 | $0.00056 | $0.00056 |
| Haiku 4.5 | $0.00028 | $0.00028 |
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 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.
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):
- Commit on a feature branch — never to
main. Conventional Commits, lowercase subject. - Push to origin (
git push -u origin HEADfor a new branch). No force-push unless the user asks. - Open or update a PR with
gh, using the account named in gitignoredCLAUDE.local.md. If a PR already exists for the branch, push updates it — do not open a duplicate. If none exists,gh pr create.- PR titles must use Conventional Commit syntax with a lowercase subject (for example,
fix: resolve login issue). Prefer deriving a single-commit PR title from its commit subject. - Verify the final title with
gh pr view --json titlebefore handoff; correct it immediately if it would fail the semantic-title check.
- PR titles must use Conventional Commit syntax with a lowercase subject (for example,
- Do not merge. The user merges PRs manually.
Skip only when the user explicitly says the work is local-only / do not share.
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 Changed · +2 lines · +68 tokens per session a81c282977d1
- 1mo ago First seen · 18 lines · 211 tokens per session scan A 16093618e40c
always-push-pr is a cursor rule published in the GitHub repository itsmemeworks/adhx (19 stars, last pushed 18d ago), licensed MIT. It adds 279 tokens to every session, about $0.0011 per session on Opus 5.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.
Other cursor rules, from other repositories
git-conventions
Git workflow and commit conventions for AI-assisted development.
api-for-yourself
Publish 'how to work with me' as a literal API spec — endpoints (what to ask me for and what you'll get back), rate limits (meeting and interrupt tolerance), error codes (what happens when you surprise me Friday 5pm), auth (how to earn trust), and a changelog. Use when onboarding to a new team, when a new manager or…
branching-strategy
GitFlow-inspired branching strategy for this project. Solo development omits the develop branch.
lint-format-guide
Cursor rule "lint-format-guide" from first-fluke/fullstack-starter, covering lint & format guide, quick commands, check all, from root and python (in apps/api or apps/worker).
e2e-testing
E2E Flow Tests setup and debugging guide.
knowledge
This file explains the Knowledge Base feature and how it's implemented.