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.
npx agentmods add rules/zhangzhefang-github/mcp-add-server/git-commands-cheatsheetgit clone --depth 1 https://github.com/zhangzhefang-github/mcp-add-serverWrote 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.
[](https://agentmods.dev/rules/zhangzhefang-github/mcp-add-server/git-commands-cheatsheet)<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="Measured on agentmods" height="20"></a>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 | $0.00000 | $0.00156 |
| Sonnet 5 | $0.00000 | $0.00062 |
| Haiku 4.5 | $0.00000 | $0.00031 |
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 4d 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.
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.
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.
- 4d ago First seen · 24 lines · 0 tokens per session scan A d598c560bc3f
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.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.