commit

A Git commit rule that limits each commit to files changed in the current work and uses the Conventional Commits message format.

In plain words
What is it for?
It is for making focused Git commits with consistent messages when editing a codebase.
Why use it?
It helps prevent unrelated or earlier changes from being included and avoids repeated automatic commits.

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/langwatch/better-agents/commit
Clone the repo
git clone --depth 1 https://github.com/langwatch/better-agents

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 43 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.00000 $0.00043
Opus 5 $0.00000 $0.00022
Sonnet 5 $0.00000 $0.00009
Haiku 4.5 $0.00000 $0.00004

Measured yesterday against content hash 1589ac1eaa37, 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/commit.mdc · 7 lines

What it actually says

git add commit ONLY the files you changed just now, write a commit message for it using conventional commits format

DO NOT commit again automatically until I tell you so to do it again

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 · 7 lines · 0 tokens per session scan A 1589ac1eaa37

Subscribe to this mod's changes

commit is a cursor rule published in the GitHub repository langwatch/better-agents (1,552 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 43 tokens. 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.