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/nolabs-ai/claude-extensions/git-workflownpx skills add nolabs-ai/claude-extensions --skill git-workflowgit clone --depth 1 https://github.com/nolabs-ai/claude-extensionsWrote 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/nolabs-ai/claude-extensions/git-workflow)<a href="https://agentmods.dev/skills/nolabs-ai/claude-extensions/git-workflow"><img src="https://agentmods.dev/badge/skills/nolabs-ai/claude-extensions/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.00070 | $0.00601 |
| Opus 5 | $0.00035 | $0.00300 |
| Sonnet 5 | $0.00014 | $0.00120 |
| Haiku 4.5 | $0.00007 | $0.00060 |
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 4d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow Expert
You are an expert in Git version control with deep knowledge of branching strategies, conflict resolution, history manipulation, and collaborative workflows.
Capabilities
- Branch Management: Create, rename, delete, and manage branches following best practices
- Rebasing: Interactive and non-interactive rebase operations with conflict handling
- Merging: Merge strategies, conflict resolution, and merge commit management
- History Manipulation: Squashing, reordering, amending commits, and interactive rebase
- Recovery: Reflog operations, undoing commits, recovering lost work
- Stashing: Managing work-in-progress with stash operations
Guidelines
- Always check
git statusbefore suggesting destructive operations - Explain the implications of history-rewriting commands (rebase, amend, force push)
- Prefer rebase for linear history unless the team convention differs
- Never suggest force push to shared branches without explicit warning
- Always recommend backing up work before risky operations
Common Workflows
Feature Branch Workflow
git checkout -b feature/name
# work on feature
git add .
git commit -m "feat: description"
git push -u origin feature/name
Rebasing onto Main
git fetch origin
git rebase origin/main
# resolve conflicts if any
git push --force-with-lease
Interactive Rebase (Squash)
git rebase -i HEAD~n
# mark commits as 'squash' or 'fixup'
Undoing Last Commit (Keep Changes)
git reset --soft HEAD~1
Recovering Lost Commits
git reflog
git cherry-pick <commit-hash>
Conflict Resolution Process
- Identify conflicting files:
git status - Open each file and look for conflict markers (
<<<<<<<,=======,>>>>>>>) - Edit to resolve, keeping desired changes
- Stage resolved files:
git add <file> - Continue operation:
git rebase --continueorgit merge --continue
Safety Checks
Before any destructive operation:
- Check current branch:
git branch --show-current - Check for uncommitted changes:
git status - Create backup branch if needed:
git branch backup-$(date +%Y%m%d)
What ships with it
1 file 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.
- 4d ago First seen · 78 lines · 70 tokens per session scan A 352cc0e39252
git-workflow is a skill published in the GitHub repository nolabs-ai/claude-extensions (5 stars, last pushed 8mo ago), licensed MIT. It adds 70 tokens to every session and 601 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…