git-workflow

Rules for handling Git, the system used to track code changes, including a workflow and recovery check.

In plain words
What is it for?
It is for guiding Git operations when the rule is active, using the project's git-workflow.md file.
Why use it?
It helps keep code changes consistent with the project's Git process and supports recovery checks when needed.

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/aigentive/ralphx/git-workflow
Clone the repo
git clone --depth 1 https://github.com/aigentive/RalphX

Made for: Cursor.

Per session 44 This file is loaded in full into every session.
When invoked 44 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.00044 $0.00044
Opus 5 $0.00022 $0.00022
Sonnet 5 $0.00009 $0.00009
Haiku 4.5 $0.00004 $0.00004

Measured yesterday against content hash 9858e3d877fc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

git-workflow 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 yesterday.

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-workflow.mdc · 9 lines

What it actually says

Git Workflow Rules

When this rule is active, read @.claude/rules/git-workflow.md and follow it.

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. yesterday First seen · 9 lines · 44 tokens per session scan A 9858e3d877fc

Subscribe to this mod's changes

git-workflow is a cursor rule published in the GitHub repository aigentive/RalphX (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 44 tokens to every session, about $0.0002 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.