What is git-commands-cheatsheet?

A quick reference for common Git commands. Git is a tool that records code changes so developers can work on versions, branches, and shared repositories.

Use it to initialize repositories, stage and commit files, inspect status and history, switch branches, merge, synchronize with a remote repository, or undo a recent commit.

It puts frequently needed commands and their effects in one place, including a warning for a command that discards local changes. This helps reduce mistakes when managing code history.

git-commands-cheatsheet — Cursor rule by zhangzhefang-github

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/zhangzhefang-github/mcp-add-server

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/zhangzhefang-github/mcp-add-server/git-commands-cheatsheet/github.svg)](https://agentmods.dev/rules/zhangzhefang-github/mcp-add-server/git-commands-cheatsheet)

Your own site

<a href="https://agentmods.dev/rules/zhangzhefang-github/mcp-add-server/git-commands-cheatsheet"><img src="https://agentmods.dev/badge/rules/zhangzhefang-github/mcp-add-server/git-commands-cheatsheet/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/zhangzhefang-github/mcp-add-server/git-commands-cheatsheet"><img src="https://agentmods.dev/badge/rules/zhangzhefang-github/mcp-add-server/git-commands-cheatsheet.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 311 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.00000	$0.00311
Opus 5.5	$0.00000	$0.00124
Sonnet 5.5	$0.00000	$0.00062
Haiku 4.5	$0.00000	$0.00031

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

Security

Grade A, and why

git-commands-cheatsheet 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 2mo 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-commands-cheatsheet.mdc · 24 lines

What it actually says

Common Git Commands

This is a quick reference for some common Git commands.

git init: Initializes a new Git repository in the current directory.
git add <file>: Adds a file to the staging area.
git add .: Adds all new and modified files in the current directory and subdirectories to the staging area.
git commit -m "commit message": Records changes to the repository with a descriptive message.
git status: Shows the status of changes as untracked, modified, or staged.
git log: Shows the commit history.
git branch <branch-name>: Creates a new branch.
git checkout <branch-name>: Switches to the specified branch.
git merge <branch-name>: Merges the specified branch into the current branch.
git pull: Fetches changes from the remote repository and merges them into the current branch.
git push: Pushes committed changes to a remote repository.
git reset --soft HEAD~1: Undoes the last commit but keeps the changes in the staging area.
git reset --hard HEAD~1: Undoes the last commit and discards the changes in the working directory and staging area. Use with caution.
git remote add origin <repository-url>: Connects your local repository to a remote server.

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.

2mo ago First seen · 24 lines · 0 tokens per session scan A d598c560bc3f

Subscribe to this mod's changes

git-commands-cheatsheet is a cursor rule published in the GitHub repository zhangzhefang-github/mcp-add-server (0 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 311 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-31.

Git and workflow

git-commands-cheatsheet

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

Common Git Commands

What this file has done since we first saw it

Other cursor rules, from other repositories

iris

rebase-only-merged-agents

git-workflow

release-checklist

git-workflow

branching-merging-strategy