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/WellApp-ai/WellWrote 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/wellapp-ai/well/push-pr)<a href="https://agentmods.dev/rules/wellapp-ai/well/push-pr"><img src="https://agentmods.dev/badge/rules/wellapp-ai/well/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/wellapp-ai/well/push-pr"><img src="https://agentmods.dev/badge/rules/wellapp-ai/well/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.00012 | $0.01920 |
| Opus 5.5 | $0.00005 | $0.00768 |
| Sonnet 5.5 | $0.00002 | $0.00384 |
| Haiku 4.5 | $0.00001 | $0.00192 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Push PR Mode (Gate 5 - Human Code Review)
Triggered by pr-threshold skill or manually. Creates PR for human review.
┌─────────────────────────────────────────────────────────────┐
│ PHASE 1: VALIDATE │
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │
│ │ Pre-Push │ → │ Detect │ → │ Assign │ │
│ │ Checks │ │ Domain │ │ Reviewer │ │
│ └─────────────┘ └─────────────┘ └─────────────┘ │
└─────────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────────┐
│ PHASE 2: PUBLISH │
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │
│ │ Push │ → │ Create PR │ → │ Update │ │
│ │ Branch │ │ │ │ Notion │ │
│ └─────────────┘ └─────────────┘ └─────────────┘ │
└─────────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────────┐
│ PHASE 3: COMMUNICATE │
│ ┌─────────────┐ ┌─────────────┐ │
│ │ Slack │ → │ Gate 5 │ ← Human review │
│ │ Announce │ │ │ (Changes → patine) │
│ └─────────────┘ └─────────────┘ │
└─────────────────────────────────────────────────────────────┘
Trigger Conditions
This mode is entered when:
- pr-threshold skill returns TRIGGER_PR
- User explicitly requests PR push
- Feature complete (100% scope from Commit Plan)
Phase 1: VALIDATE
1.1 Quality Gates
Invoke code-review skill Phase 0 (pre-push validation):
-
npm run typecheck- No type errors -
npm run lint- No lint errors - No console.log in changed files
If any check fails, fix issues before continuing.
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 · 291 lines · 12 tokens per session scan A d83e9768daf5
push-pr is a cursor rule published in the GitHub repository WellApp-ai/Well (345 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 1,920 once invoked, about $0.0000 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
Never mutate git history, remotes, or GitHub repo state.
commit-message-format
Applied when creating Git commit messages. Format rules for Conventional Commits-based Prefix + English summary + bulleted body.
pr-message-format
Applied when creating Pull Requests. Format rules for Prefix + English summary + structured body (overview, changes, test content).
git_conventions
Git-related rules and best practices for version control.
rebase-only-merged-agents
When rebasing after a merge, only rebase the agents whose branches you just merged. Do not rebase agents that are still running.
branching-merging-strategy
This is a set of instructions to the AI Assistant for branching and merging strategy.