git-safety

git-safety is a cursor rule for Cursor from hlalljie/agent-workflow-presets. It costs 226 tokens per session, scanned A, original, MIT.

A set of rules that controls when an agent may stage files, create commits, open pull requests, or push changes with Git, a tool for tracking code history.

In plain words
What is it for?
It is for keeping Git changes behind a defined commit or pull-request process, especially during automated coding work.
Why use it?
It prevents accidental commits, pull requests, or uploads and requires explicit approval for a proposed commit message.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/hlalljie/agent-workflow-presets/git-safety
Clone the repo
git clone --depth 1 https://github.com/hlalljie/agent-workflow-presets

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 git-safety

README.md
[![agentmods](https://agentmods.dev/badge/rules/hlalljie/agent-workflow-presets/git-safety.svg)](https://agentmods.dev/rules/hlalljie/agent-workflow-presets/git-safety)
Your own site
<a href="https://agentmods.dev/rules/hlalljie/agent-workflow-presets/git-safety"><img src="https://agentmods.dev/badge/rules/hlalljie/agent-workflow-presets/git-safety.svg" alt="Measured on agentmods" height="20"></a>
Per session 226 This file is loaded in full into every session.
When invoked 226 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00226 $0.00226
Opus 5 $0.00113 $0.00113
Sonnet 5 $0.00045 $0.00045
Haiku 4.5 $0.00023 $0.00023

Measured 3d ago against content hash b6ca7612dc82, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

git-safety 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.

.cursor/rules/git-safety.mdc · 14 lines

What it actually says

Never run git add, git commit, gh pr create, or git push directly.

If the user wants to commit, follow the commit skill. If the user wants a PR, follow the pr skill.

"go ahead", "do it", "yes", or any approval that comes in the same message as a request to make changes is approval of the changes only — not approval to commit. Committing always requires a response that refers specifically to the commit proposal (e.g. "y", "yes", "approved", "use that message") — not a general affirmative that could be responding to anything else visible in the conversation.

Never commit as part of a task loop, cleanup, or reorganization step unless the commit skill has been explicitly invoked and the user has approved the proposed message with a response clearly directed at the commit proposal.

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. 3d ago First seen · 14 lines · 226 tokens per session scan A b6ca7612dc82

Subscribe to this mod's changes

git-safety is a cursor rule published in the GitHub repository hlalljie/agent-workflow-presets (2 stars, last pushed 1mo ago), licensed MIT. It adds 226 tokens to every session, about $0.0011 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-31.