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 skills/projanvil/mindforge/git-gurunpx skills add ProjAnvil/MindForge --skill git-gurugit clone --depth 1 https://github.com/ProjAnvil/MindForgeWhat 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.00070 | $0.03066 |
| Opus 5 | $0.00035 | $0.01533 |
| Sonnet 5 | $0.00014 | $0.00613 |
| Haiku 4.5 | $0.00007 | $0.00307 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 491 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.
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
Reorder Commits
git rebase -i HEAD~5
# In editor, reorder:
# pick def456 Was second
# pick abc123 Was first
# pick ghi789 Was third
# Result: Commits in new order
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.
- yesterday 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 5mo ago), licensed MIT. It adds 70 tokens to every session and 3,066 once invoked, about $0.0003 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 skills, from other repositories
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — errors, failed tool calls, latency, regressions, and low online-eval scores — plus Diagnostics issues. Reads live/production traces via the SDK (searchtraces and agentinsights) and works with no MCP; uses the MCP issue entity when connected.…
client-scripts
Write ServiceNow client scripts (onLoad/onChange/onSubmit/onCellEdit) using gform, guser, GlideAjax, field visibility/mandatory toggles, and validation with debounced server calls.
agoragentic-transaction-assurance
Prepare, evaluate, and reconcile autonomous agent transactions without self-granting payment or owner authority. Use when an agent must bind principal authority, seller terms, payment evidence, execution, delivered outcome, and reconciliation; handle paid retries safely; or prepare an authority request for owner…
linkding
Manage bookmarks with Linkding. Use when the user asks to "save a bookmark", "add link", "search bookmarks", "list my bookmarks", "find saved links", "tag a bookmark", "archive bookmark", "check if URL is saved", "list tags", "create bundle", or mentions Linkding bookmark management.
debugging-mutations
Verify what changed on a ServiceNow instance after a tool call — sysaudit inspection, syslog/transaction logs, session context, Flow Designer execution logs, outbound HTTP traces.
maya-shot-export
Pipeline stage — shot-level export: frame ranges, cameras, FBX / Alembic packaging for editorial. Use when packaging shot data for downstream departments. Not for full pipeline publish (maya-pipeline) or scene assembly (maya-scene-assembly).