git_commit

A rule for naming Git commits, which record changes made to a code project.

In plain words
What is it for?
Use it when creating commits: choose a lowercase English prefix such as fix or feat, add details when needed, and commit without pushing.
Why use it?
It keeps commit history consistent and prevents accidental publishing of changes without approval.

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/benyue1978/solo-flow-mcp/git_commit
Clone the repo
git clone --depth 1 https://github.com/benyue1978/solo-flow-mcp

Made for: Cursor.

Per session 3 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 213 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.00003 $0.00213
Opus 5 $0.00002 $0.00106
Sonnet 5 $0.00001 $0.00043
Haiku 4.5 $0.00000 $0.00021

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

Security

Grade A, and why

git_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/git_commit.mdc · 31 lines

What it actually says

Git Usage

  • Use the following prefixes for commit messages, followed by a colon and a space:

    • fix — for bug fixes
    • feat — for new features
    • perf — for performance improvements
    • docs — for documentation changes
    • style — for formatting changes
    • refactor — for code refactoring
    • test — for adding missing tests
    • chore — for routine tasks
  • When determining the commit message prefix, pick the most relevant option from the list above.

  • Use lowercase for all commit messages.

  • Use English for all commit messages.

  • If the change is not self-explanatory, include a bullet list of changes after a blank line below the summary.

  • Commit but not push. You can only push after my approval.


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 · 31 lines · 3 tokens per session scan A d588ad5a35eb

Subscribe to this mod's changes

git_commit is a cursor rule published in the GitHub repository benyue1978/solo-flow-mcp (1 stars, last pushed 1y ago), licensed MIT. It adds 3 tokens to every session and 213 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-31.