A rule for running Git commands without opening an interactive pager, which is a screen that pauses long command output.

It applies to commands such as log, diff, show, and blame, including commands whose output is piped into another command.

It keeps Git output complete and usable in automated tools and scripts.

git — Cursor rule for Cursor by mitas/cursor-rules

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/mitas/cursor-rules

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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/mitas/cursor-rules/git/github.svg)](https://agentmods.dev/rules/mitas/cursor-rules/git)

Your own site

<a href="https://agentmods.dev/rules/mitas/cursor-rules/git"><img src="https://agentmods.dev/badge/rules/mitas/cursor-rules/git/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/mitas/cursor-rules/git"><img src="https://agentmods.dev/badge/rules/mitas/cursor-rules/git.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 438 The whole file, excluding the scripts and references it only reads on demand.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00006	$0.00438
Opus 5.5	$0.00002	$0.00175
Sonnet 5.5	$0.00001	$0.00088
Haiku 4.5	$0.00001	$0.00044

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

Security

Grade A, and why

git 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/git.mdc · 47 lines

What it actually says

Git Command Usage

Context

Git commands may invoke a pager that can cause issues in automated environments or tool calls.
Terminal outputs from git commands can be difficult to capture when pager is active.
Proper git command formatting improves consistency and predictability.
The --no-pager flag prevents git from using the pager program for output.
This rule ensures git output is directly printed to standard output without interruption.

Critical rules

Always use git --no-pager when executing git commands in automated environments.
Use git --no-pager log instead of git log to avoid pager prompts.
Use git --no-pager diff instead of git diff to see full output without pagination.
Use git --no-pager show instead of git show to view commits without pager interference.
Use git --no-pager blame instead of git blame for uninterrupted blame information.
When piping git output (e.g., git log | grep pattern), always include the --no-pager flag.
For git commands that produce large outputs, consider adding limits (e.g., git --no-pager log -n 10).
The --no-pager flag should appear immediately after git and before the subcommand.
Terminal commands involving git that would use a pager should always include the --no-pager flag.
When creating git aliases, incorporate the --no-pager flag for commands that typically use pagers.

Examples

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.

1mo ago First seen · 47 lines · 6 tokens per session scan A 56f959a49767

Subscribe to this mod's changes

git is a cursor rule published in the GitHub repository mitas/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It adds 6 tokens to every session and 438 once invoked, about $0.0000 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.

Git and workflow

git

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Git Command Usage

Context

Critical rules

Examples

What this file has done since we first saw it

Other cursor rules, from other repositories

rebase-only-merged-agents

iris

git-workflow

release-checklist

git-workflow

branching-merging-strategy