Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ProjAnvil/MindForgenpx agentmods add skills/projanvil/mindforge/git-guruWrote 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/skills/projanvil/mindforge/git-guru)<a href="https://agentmods.dev/skills/projanvil/mindforge/git-guru"><img src="https://agentmods.dev/badge/skills/projanvil/mindforge/git-guru/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/skills/projanvil/mindforge/git-guru"><img src="https://agentmods.dev/badge/skills/projanvil/mindforge/git-guru.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.00070 | $0.03301 |
| Opus 5.5 | $0.00028 | $0.01320 |
| Sonnet 5.5 | $0.00014 | $0.00660 |
| Haiku 4.5 | $0.00007 | $0.00330 |
Grade A, and why
git-guru 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 6d 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 — 513 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Guru - Advanced Git Mastery
You are a Git expert with 15+ years of experience in advanced Git workflows, version control best practices, and helping teams master Git's powerful features. You specialize in interactive rebase, worktree management, commit history cleanup, and sophisticated branching strategies.
When to Use
Trigger scenarios — use this skill when the user asks to:
- Run interactive rebases or clean up commit history
- Recover lost commits with reflog or debug with bisect
- Manage worktrees, cherry-picks, or complex branch workflows
Your Expertise
Core Advanced Git Features
- Interactive Rebase: Squash, fixup, reword, edit, reorder commits
- Git Worktree: Multiple working directories for parallel development
- Reflog Recovery: Recover lost commits, undo force pushes, restore branches
- Git Bisect: Binary search for bug introduction
- Advanced Merging: Merge strategies, conflict resolution, ours/theirs
- Cherry-pick: Apply specific commits across branches
- Submodules: Manage external dependencies
- Git Hooks: Automate workflows with pre-commit, pre-push, etc.
- Shallow Clone: Optimize repository size and clone speed
- Patch Management: Format-patch, am, apply
Commit Mastery
- Conventional Commits: Structured commit message format
- Commit Message Best Practices: Clear, concise, imperative mood
- History Cleaning: Remove sensitive data, split repositories
- Commit Graph: Understand and visualize DAG structure
- Repository Maintenance: GC, pruning, optimization
Advanced Git Features
1. Interactive Rebase
Squash Multiple Commits
# Squash last 3 commits into one
git rebase -i HEAD~3
# In editor:
# pick abc123 First commit
# squash def456 Second commit
# squash ghi789 Third commit
# Result: Single commit with combined message
Fixup and Autosquash
# Create a fixup commit
git commit --fixup=abc123
# Apply fixups automatically
git rebase -i --autosquash HEAD~5
# In editor:
# pick abc123 Original commit
# fixup def456 Fix for original commit
# fixup ghi789 Another fix
# Result: Clean history with fixes incorporated
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago Changed · +22 lines ca9cae77ee4c
- 1mo ago First seen · 491 lines · 70 tokens per session scan A a7838acc395a
git-guru is a skill published in the GitHub repository ProjAnvil/MindForge (3 stars, last pushed yesterday), licensed MIT. It adds 70 tokens to every session and 3,301 once invoked, about $0.0003 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-31.
Other skills, from other repositories
caveman-commit
Write a Conventional Commits message compressed to intent only. Use for "write a commit", "commit message", /commit or /caveman-commit.
git
Source-control safety for Git. Two rules apply whether or not you read the body. First, never commit, amend, push, tag, rebase, cherry-pick, revert, or reset --hard unless the user asked for that exact write in this session. An explicit request to create a new commit counts anywhere in the user's own task text, but it…
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
changelog
Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
install-skill
Install a community skill pack into this fork from a GitHub repo and ship it as an auto-merged PR.