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/d-padmanabhan/agent-engineering-handbook/130-gitgit clone --depth 1 https://github.com/d-padmanabhan/agent-engineering-handbookWrote 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/d-padmanabhan/agent-engineering-handbook/130-git)<a href="https://agentmods.dev/rules/d-padmanabhan/agent-engineering-handbook/130-git"><img src="https://agentmods.dev/badge/rules/d-padmanabhan/agent-engineering-handbook/130-git.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 | $0.00866 | $0.00866 |
| Opus 5 | $0.00433 | $0.00433 |
| Sonnet 5 | $0.00173 | $0.00173 |
| Haiku 4.5 | $0.00087 | $0.00087 |
Grade A, and why
130-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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Agent Gates
This rule contains only mandatory policy. Use the Git workflow skill (${HANDBOOK_ROOT}/skills/git-workflow/SKILL.md) for procedures, command sequences, examples, recovery, branch strategy, and commit formatting.
Preserve User Work
- Inspect
git status --short, the current branch, andHEADbefore repository edits. - Preserve unrelated staged, unstaged, and untracked changes.
- Never run a worktree-discard operation unless the user explicitly authorizes the exact command and affected paths:
git restoregit checkout -- <path>git reset --hardgit clean -f
- Do not stash user work merely to simplify the agent's workflow. Use a stash only when the operation genuinely requires a clean tree, explain its contents, and restore it promptly.
- Do not delete branches, remove worktrees, or rewrite shared history without explicit authorization.
The broader checkpoint, verification, remote-mutation, and audit policy is canonical in 020-agent-audit.mdc (${HANDBOOK_ROOT}/rules/020-agent-audit.mdc).
Commit Authorization and Signing
Before executing git commit:
-
Run applicable tests, lint, formatting, type checks, and build/package checks.
-
Show the complete commit message:
==================== COMMIT MESSAGE PREVIEW ==================== <type>(<scope>): <imperative summary> - <Key change> - <Key change> <Optional rationale> ================================================================ -
Show the exact staged file list, including added, modified, renamed, and deleted files.
-
Ask for explicit confirmation and wait for it.
Commit messages use Conventional Commits, an imperative summary of at most 72 characters, and concise rationale-focused bullets when useful. Detailed formats and examples live in the Git workflow reference (${HANDBOOK_ROOT}/skills/git-workflow/git-workflow.md).
Cryptographic commit signing is mandatory unless the repository documents an explicit exception:
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.
- 3d ago First seen · 78 lines · 866 tokens per session scan A 2fb7307136f1
130-git is a cursor rule published in the GitHub repository d-padmanabhan/agent-engineering-handbook (16 stars, last pushed 4d ago), licensed MIT. It adds 866 tokens to every session, about $0.0043 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-30.
Other cursor rules, from other repositories
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.
family-instance-domain-actions
Family instance domain action implementation patterns.