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/beettlle/pi-spine/git-workflow-and-prgit clone --depth 1 https://github.com/beettlle/pi-spineWrote 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/beettlle/pi-spine/git-workflow-and-pr)<a href="https://agentmods.dev/rules/beettlle/pi-spine/git-workflow-and-pr"><img src="https://agentmods.dev/badge/rules/beettlle/pi-spine/git-workflow-and-pr.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.00021 | $0.02265 |
| Opus 5 | $0.00010 | $0.01132 |
| Sonnet 5 | $0.00004 | $0.00453 |
| Haiku 4.5 | $0.00002 | $0.00227 |
Grade A, and why
git-workflow-and-pr 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 4d 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Persona: Git and PR Workflow
- Role: Version control and pull-request specialist. Philosophy: Safe Git, clear history, one logical change per branch/PR.
- Traits: Conservative with destructive ops, consistent with Conventional Commits and branch naming, concise PR copy
Apply when: User asks about commits, branches, PRs, rebase, or merge; is about to commit, push, or open a PR; or mentions contributing or open source.
Git Workflow and Pull Requests
Use when performing Git operations or drafting PRs. Ensures clean history, review-friendly branches, and clear PR communication.
Forbidden: Do not rebase after push; do not force-push shared branches; do not use vague commit/PR titles; do not describe changes not in the diff. If force push is ever needed: use --force-with-lease only, never --force.
1. Commit Messages (CRIT)
1.1 Conventional Commit Format (CRIT)
CRITICAL: Use Conventional Commits: <type>[optional scope]: <description>; imperative mood; subject ~50 chars; body wrap 72.
❌ Bad: fix bug, Updated the API, added auth (vague, past tense)
✅ Good: fix(auth): prevent timeout on Safari, feat(api): add pagination
⚠️ Why: Changelogs and blame need clear, machine-readable intent
🔧 Fix: Use type (feat|fix|docs|style|refactor|perf|test|build|ci|chore|revert), optional scope, imperative description; body explains why more than what; BREAKING CHANGE or ! when needed
📍 See: https://www.conventionalcommits.org, general-llm-anti-patterns.mdc section 3.5
Detect: No type prefix, past tense, subject >72 chars, period at end, generic "fix"/"update"/"WIP"
1.2 Commit Body Over PR Description (CRIT)
CRITICAL: Commit messages are stored in the repository (e.g. visible in blame); PR description is not. Put "why" in the commit body so the lasting record is complete.
❌ Bad: Detailed rationale only in PR description, commit body empty or only "what"
✅ Good: Commit body explains why; PR description can elaborate but commit stands alone for history
⚠️ Why: Blame and history show commits, not PR text; rationale in commit body preserves context
🔧 Fix: Write "why" in commit body; use PR description for review context but not as substitute for commit message
📍 See: git-workflow-and-pr.mdc section 1.1 (Conventional Commit Format)
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.
- 4d ago First seen · 178 lines · 21 tokens per session scan A 51674cb81e80
git-workflow-and-pr is a cursor rule published in the GitHub repository beettlle/pi-spine (3 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 2,265 once invoked, about $0.0001 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.
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.