commit

Commit rules requiring review and quality checks before changes are saved to Git.

In plain words
What is it for?
Use them to run pull-request review and QA checks, assess risks, debug failures, and commit only when validation passes.
Why use it?
They help catch runtime, type, lint, requirement, and quality problems before a commit is created.

Cursor rule

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/wellapp-ai/well/commit
Clone the repo
git clone --depth 1 https://github.com/WellApp-ai/Well
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 971 The whole file, excluding the scripts and references it only reads on demand.
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.00008 $0.00971
Opus 5 $0.00004 $0.00485
Sonnet 5 $0.00002 $0.00194
Haiku 4.5 $0.00001 $0.00097

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

Security

Grade A, and why

commit 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/modes/commit.mdc · 167 lines

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.

Commit Rules

Before committing, invoke validation skills to ensure quality.

Pre-Commit Workflow

┌─────────────────────────────────────────────────────────────┐
│  1. Invoke pr-review skill                                  │
│     - Runtime check (Docker, API, Web) - auto-resolve       │
│     - TypeCheck, Lint, ReadLints                            │
│     - Risk assessment                                       │
│     - Verdict: PASS/WARN/BLOCK                              │
└─────────────────────────────────────────────────────────────┘
                           ↓
┌─────────────────────────────────────────────────────────────┐
│  2. Invoke qa-commit skill                                  │
│     - Verify Satisfies criteria (G#N, AC#N)                 │
│     - Verdict: GREEN/RED                                    │
│     - If RED: Auto-invoke debug skill                       │
└─────────────────────────────────────────────────────────────┘
                           ↓
┌─────────────────────────────────────────────────────────────┐
│  3. Git Commit (if all pass)                                │
│     - Message format                                        │
│     - Include Satisfies field                               │
└─────────────────────────────────────────────────────────────┘
                           ↓
┌─────────────────────────────────────────────────────────────┐
│  4. Invoke pr-threshold skill                               │
│     - Check accumulated metrics                             │
│     - Verdict: CONTINUE/TRIGGER_PR                          │
└─────────────────────────────────────────────────────────────┘

Step 1: Invoke pr-review Skill

Before committing:

Invoking pr-review skill...

Required checks:

  • Runtime environment ready (Docker, API:8080, Web:3000)
  • npm run typecheck passes
  • npm run lint passes
  • ReadLints shows no errors on changed files
  • No console.log in changed files

Read the full file on GitHub · 167 lines

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 · 167 lines · 8 tokens per session scan A c438a11ff01f

Subscribe to this mod's changes

commit is a cursor rule published in the GitHub repository WellApp-ai/Well (341 stars, last pushed 25d ago), licensed MIT. It adds 8 tokens to every session and 971 once invoked, about $0.0000 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.