commit

A set of instructions for recording code changes in Git with one Conventional Commits message, a standard format for describing commits.

In plain words
What is it for?
Use it when staging or committing changes in the working tree.
Why use it?
It helps keep changes staged and commit messages consistent and understandable.

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/khrichtchatyi/ship-it/commit
Clone the repo
git clone --depth 1 https://github.com/khrichtchatyi/ship-it

Made for: Cursor.

Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 88 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.00029 $0.00088
Opus 5 $0.00015 $0.00044
Sonnet 5 $0.00006 $0.00018
Haiku 4.5 $0.00003 $0.00009

Measured yesterday against content hash 279f6ad6ec9e, 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

The authoritative instructions for this skill live in skills/commit/SKILL.md. Read that file in full and follow it when the user asks to commit changes; do not improvise a shortened workflow.

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 · 29 tokens per session scan A 279f6ad6ec9e

Subscribe to this mod's changes

commit is a cursor rule published in the GitHub repository khrichtchatyi/ship-it (2 stars, last pushed 19d ago), licensed MIT. It adds 29 tokens to every session and 88 once invoked, about $0.0001 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-31.