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.
git clone --depth 1 https://github.com/MCKRUZ/claude-code-masteryWrote 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/mckruz/claude-code-mastery/git-workflow)<a href="https://agentmods.dev/rules/mckruz/claude-code-mastery/git-workflow"><img src="https://agentmods.dev/badge/rules/mckruz/claude-code-mastery/git-workflow/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/mckruz/claude-code-mastery/git-workflow"><img src="https://agentmods.dev/badge/rules/mckruz/claude-code-mastery/git-workflow.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00232 | $0.00232 |
| Opus 5.5 | $0.00093 | $0.00093 |
| Sonnet 5.5 | $0.00046 | $0.00046 |
| Haiku 4.5 | $0.00023 | $0.00023 |
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 1mo 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.
What it actually says
Git & Workflow
Planning
- Plan before coding on any non-trivial task (3+ files or unclear requirements).
- For complex features (5+ files, new services): outline the approach and get approval before implementing.
- Review your own work before marking anything as done.
Commit Messages
Format: type: description (feat, fix, refactor, docs, test, chore, perf, ci)
- Imperative mood, lowercase, no period at end
- Under 72 characters
- Body optional — explain "why" not "what" when included
PR Workflow
- Analyze full commit history with
git diff [base-branch]...HEAD - Draft comprehensive summary with test plan
- Push with
-uflag if new branch - PR title under 70 characters — use description for details
Branch Hygiene
- Never force-push to main/master
- Never commit secrets, .env files, or credentials
- Use feature branches for all work
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.
- 1mo ago First seen · 29 lines · 232 tokens per session scan A 784e371c8f3f
git-workflow is a cursor rule published in the GitHub repository MCKRUZ/claude-code-mastery (11 stars, last pushed 5mo ago), licensed MIT. It adds 232 tokens to every session, about $0.0009 per session on Opus 5.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
caliber-pre-commit
Run Caliber sync before git commits to keep agent configs up to date.
git-conventions
Apply when committing, branching, or opening a pull request. Conventional commit format, branch naming, PR scope.
cursorrules
A collection of project rules for Cursor, an AI coding editor. The rules cover money and date formats, error handling, types, comments, linting, and safe Git use.
pr-standards
Git Commit & PR Standards for AI-Assisted Development.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.