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/cembasaranoglu/crafting-system-claude/60-git-workflowgit clone --depth 1 https://github.com/cembasaranoglu/crafting-system-claudeWrote 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/cembasaranoglu/crafting-system-claude/60-git-workflow)<a href="https://agentmods.dev/rules/cembasaranoglu/crafting-system-claude/60-git-workflow"><img src="https://agentmods.dev/badge/rules/cembasaranoglu/crafting-system-claude/60-git-workflow.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.00024 | $0.00101 |
| Opus 5 | $0.00012 | $0.00051 |
| Sonnet 5 | $0.00005 | $0.00020 |
| Haiku 4.5 | $0.00002 | $0.00010 |
Grade A, and why
60-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.
What it actually says
Before git add/commit/push: inspect branch, status, diff, untracked files, and staged files. Do not stage secrets, local configs, logs, caches, assistant artifacts, or large binaries. Do not push, force-push, reset hard, clean, rebase public branches, or delete branches without explicit current authorization.
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.
- yesterday First seen · 8 lines · 24 tokens per session scan A f0c7318d44e1
60-git-workflow is a cursor rule published in the GitHub repository cembasaranoglu/crafting-system-claude (5 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 101 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-09-03.
Other cursor rules, from other repositories
git
Conventional commit message format for git commits.
no-ai-attribution
Never attribute commits, comments, or contributions to AI agents.
git-commit-attribution
Git commits must use the human developer identity only; never Cursor Agent co-authorship.
commit-sponsors
Every git commit message must acknowledge BetterDesk supporters.
git_workflow
Git Workflow and Configuration for AGB SDK.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.