01-git-workflow

01-git-workflow is a cursor rule for Cursor from bybren-llc/a-safe-pulse. It costs 669 tokens per session, scanned A, a copy of 01-git-workflow, MIT.

Git workflow rules define how to name branches, format commits, rebase changes, and create pull requests. A branch is a separate line of development, while a pull request is a review request for proposed changes.

In plain words
What is it for?
Use them for every Git operation, especially when creating branches, writing commits, rebasing, or preparing a pull request for a ticket.
Why use it?
They give the repository a consistent history and let automated checks reject branches or commits that do not meet the project's format.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use them for every Git operation, especially when creating branches, writing commits, rebasing, or preparing a pull request for a ticket.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/bybren-llc/a-safe-pulse/01-git-workflow
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.

Clone the repo
git clone --depth 1 https://github.com/bybren-llc/a-safe-pulse

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 01-git-workflow

README.md
[![agentmods](https://agentmods.dev/badge/rules/bybren-llc/a-safe-pulse/01-git-workflow.svg)](https://agentmods.dev/rules/bybren-llc/a-safe-pulse/01-git-workflow)
Your own site
<a href="https://agentmods.dev/rules/bybren-llc/a-safe-pulse/01-git-workflow"><img src="https://agentmods.dev/badge/rules/bybren-llc/a-safe-pulse/01-git-workflow.svg" alt="Measured on agentmods" height="20"></a>
Per session 669 This file is loaded in full into every session.
When invoked 669 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 88% copy Near-identical to another mod 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.1 $0.00669 $0.00669
Opus 5 $0.00334 $0.00334
Sonnet 5 $0.00134 $0.00134
Haiku 4.5 $0.00067 $0.00067

Measured 2d ago against content hash d1fef32b5971, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

01-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 2d 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.

Origin

This is a copy

88% identical to 01-git-workflow — 30 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.cursor/rules/01-git-workflow.mdc · 93 lines

How it starts

The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Git Workflow

This project enforces a rebase-first workflow validated by CI/CD automation. See CONTRIBUTING.md for the full guide.

Branch Naming

Required format: ASP-{number}-{short-description}

Examples:

  • ASP-42-add-user-authentication
  • ASP-57-fix-profile-image-upload

Rules:

  • MUST start with ASP-{number}
  • Use lowercase letters and hyphens only
  • Keep total length under 50 characters
  • Never include personal names or dates
  • CI will reject branches that do not follow this format

Commit Message Format

Required format: type(scope): description [ASP-XXX]

Types

  • feat -- New feature
  • fix -- Bug fix
  • docs -- Documentation changes
  • style -- Code formatting (no logic changes)
  • refactor -- Code restructuring
  • test -- Adding or updating tests
  • chore -- Maintenance tasks, dependencies
  • ci -- CI/CD pipeline changes

Scopes (optional)

  • auth, api, db, cli, agent, webhook, sync, security, cursor

Examples

feat(api): add planning session endpoint [ASP-42]
fix(auth): resolve login redirect issue [ASP-57]
docs: update API documentation [ASP-123]

CI will reject commits that do not include a ticket reference.

Workflow Steps

# 1. Start from latest base branch
git checkout dev
git pull origin dev
git checkout -b ASP-{number}-{description}

# 2. Make changes and commit
git add <files>
git commit -m "feat(scope): description [ASP-XXX]"

# 3. Keep branch updated (rebase, NEVER merge)
git fetch origin
git rebase origin/dev

# 4. Validate before pushing
# Run: {{CI_VALIDATE_COMMAND}}

# 5. Push
git push --force-with-lease origin ASP-{number}-{description}

# 6. Create PR using .github/pull_request_template.md
# 7. Merge using "Rebase and merge" ONLY (never squash or merge commit)

Rules

  • Rebase-first: Never create merge commits. Always rebase onto the base branch.
  • Force-with-lease: Use --force-with-lease after rebase, never --force.
  • Linear history: The project requires a clean linear commit history.
  • One ticket per branch: Each branch maps to exactly one project management ticket.
  • PR template: Always use .github/pull_request_template.md and fill ALL sections.

Read the full file on GitHub · 93 lines

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. 2d ago First seen · 93 lines · 669 tokens per session scan A d1fef32b5971

Subscribe to this mod's changes

01-git-workflow is a cursor rule published in the GitHub repository bybren-llc/a-safe-pulse (9 stars, last pushed 5mo ago), licensed MIT. It adds 669 tokens to every session, about $0.0033 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to 01-git-workflow, differing in 30 lines, and is treated as a copy.