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/bybren-llc/safe-agentic-workflow/01-git-workflowgit clone --depth 1 https://github.com/bybren-llc/safe-agentic-workflowWhat 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.00716 | $0.00716 |
| Opus 5 | $0.00358 | $0.00358 |
| Sonnet 5 | $0.00143 | $0.00143 |
| Haiku 4.5 | $0.00072 | $0.00072 |
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.
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: {{TICKET_PREFIX}}-{number}-{short-description}
Examples:
{{TICKET_PREFIX}}-42-add-user-authentication{{TICKET_PREFIX}}-57-fix-profile-image-upload
Rules:
- MUST start with
{{TICKET_PREFIX}}-{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 [{{TICKET_PREFIX}}-XXX]
Types
feat-- New featurefix-- Bug fixdocs-- Documentation changesstyle-- Code formatting (no logic changes)refactor-- Code restructuringtest-- Adding or updating testschore-- Maintenance tasks, dependenciesci-- CI/CD pipeline changes
Scopes (optional)
payments,auth,ui,api,db,scheduler,security,cursor
Examples
feat(payments): add Stripe checkout integration [{{TICKET_PREFIX}}-42]
fix(auth): resolve login redirect issue [{{TICKET_PREFIX}}-57]
docs: update API documentation [{{TICKET_PREFIX}}-123]
CI will reject commits that do not include a ticket reference.
Workflow Steps
# 1. Start from latest base branch
git checkout {{MAIN_BRANCH}}
git pull origin {{MAIN_BRANCH}}
git checkout -b {{TICKET_PREFIX}}-{number}-{description}
# 2. Make changes and commit
git add <files>
git commit -m "feat(scope): description [{{TICKET_PREFIX}}-XXX]"
# 3. Keep branch updated (rebase, NEVER merge)
git fetch origin
git rebase origin/{{MAIN_BRANCH}}
# 4. Validate before pushing
# Run: {{CI_VALIDATE_COMMAND}}
# 5. Push
git push --force-with-lease origin {{TICKET_PREFIX}}-{number}-{description}
# 6. Create PR using .github/pull_request_template.md
# 7. Merge using "Rebase and merge" ONLY (never squash or merge commit)
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.
- 2d ago First seen · 93 lines · 716 tokens per session scan A a8a2efb59069
01-git-workflow is a cursor rule published in the GitHub repository bybren-llc/safe-agentic-workflow (404 stars, last pushed 1mo ago), licensed MIT. It adds 716 tokens to every session, about $0.0036 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.
Other cursor rules, from other repositories
hedgehog
Hedgehog build discipline — how to work in this repo.
no-auto-commit
Never commit or push without explicit user instruction.
pr-standards
Git Commit & PR Standards for AI-Assisted Development.
git-commit-attribution
Git commits must use the human developer identity only; never Cursor Agent co-authorship.
git-conventional-commits
Conventional commit messages and logical multi-commit workflow when working with Git.
pause
Checkpoint the session into git so it survives a close and resumes from any device. Use on "pause", "checkpoint", "cache this session", "save my place", or "I'm stepping away" — writes a handoff, commits work in flight, and pushes.