git-workflow

Rules for common Git work, including commits, commit messages, branches, merge requests, and branching strategy. Git is a tool for tracking code changes, while branches let developers work on changes separately.

In plain words
What is it for?
Use it when creating commits, naming branches, writing commit messages, opening merge requests, or deciding how Git work should be organized.
Why use it?
It provides a consistent process for recording and organizing code changes. This helps reduce confusion when developing features, fixes, or refactors with others.

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

Made for: Cursor.

Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 806 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.00034 $0.00806
Opus 5 $0.00017 $0.00403
Sonnet 5 $0.00007 $0.00161
Haiku 4.5 $0.00003 $0.00081

Measured yesterday against content hash 168603335e1f, 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.

frontend/magic-web/.cursor/rules/git-workflow.mdc · 94 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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 · 94 lines · 34 tokens per session scan A 168603335e1f

Subscribe to this mod's changes

git-workflow is a cursor rule published in the GitHub repository dtyq/magic (4,996 stars, last pushed 20d ago), with no licence file. It adds 34 tokens to every session and 806 once invoked, 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-30.