020-review-before-commit

020-review-before-commit is a cursor rule for Cursor from pblagoje/mcp-ollama-python. It costs 129 tokens per session, scanned A, original, MIT.

A repository rule requiring the user to review changes before any Git commit, push, or pull request. Git is a system for tracking code changes and sharing them with others.

In plain words
What is it for?
Use it after code changes to show the affected files and diff, then wait for explicit permission before committing, pushing, or opening a pull request.
Why use it?
It keeps potentially irreversible or externally visible version-control actions under the user's control.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it after code changes to show the affected files and diff, then wait for explicit permission before committing, pushing, or opening a pull request.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/pblagoje/mcp-ollama-python/020-review-before-commit
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.

Clone the repo
git clone --depth 1 https://github.com/pblagoje/mcp-ollama-python

Made for: Cursor.

Wrote 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.

agentmods badge for 020-review-before-commit

README.md
[![agentmods](https://agentmods.dev/badge/rules/pblagoje/mcp-ollama-python/020-review-before-commit/github.svg)](https://agentmods.dev/rules/pblagoje/mcp-ollama-python/020-review-before-commit)
Your own site
<a href="https://agentmods.dev/rules/pblagoje/mcp-ollama-python/020-review-before-commit"><img src="https://agentmods.dev/badge/rules/pblagoje/mcp-ollama-python/020-review-before-commit/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.

agentmods 80×15 button for 020-review-before-commit

Your own site · 80×15
<a href="https://agentmods.dev/rules/pblagoje/mcp-ollama-python/020-review-before-commit"><img src="https://agentmods.dev/badge/rules/pblagoje/mcp-ollama-python/020-review-before-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 129 This file is loaded in full into every session.
When invoked 129 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00129 $0.00129
Opus 5.5 $0.00052 $0.00052
Sonnet 5.5 $0.00026 $0.00026
Haiku 4.5 $0.00013 $0.00013

Measured 1mo ago against content hash da64f6a50015, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

020-review-before-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 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.

.cursor/rules/020-review-before-commit.mdc · 12 lines

What it actually says

Review before commit

  • Never run git commit, git push, or create a PR unless the user explicitly asks in the current message.
  • After making code changes, summarize what changed and point the user to the diff (Source Control / git diff) so they can review before committing.
  • If the user asks to commit, show the planned commit message and affected files first; wait for confirmation if they asked to review changes first.
  • Do not amend, force-push, or skip hooks unless the user explicitly requests it.
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. 1mo ago First seen · 12 lines · 129 tokens per session scan A da64f6a50015

Subscribe to this mod's changes

020-review-before-commit is a cursor rule published in the GitHub repository pblagoje/mcp-ollama-python (5 stars, last pushed 15d ago), licensed MIT. It adds 129 tokens to every session, about $0.0005 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-31.