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 agents/sagargupta16/claude-skills/git-assistantgit clone --depth 1 https://github.com/Sagargupta16/claude-skillsWrote 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/agents/sagargupta16/claude-skills/git-assistant)<a href="https://agentmods.dev/agents/sagargupta16/claude-skills/git-assistant"><img src="https://agentmods.dev/badge/agents/sagargupta16/claude-skills/git-assistant.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.1 | $0.00087 | $0.00422 |
| Opus 5 | $0.00044 | $0.00211 |
| Sonnet 5 | $0.00017 | $0.00084 |
| Haiku 4.5 | $0.00009 | $0.00042 |
Grade A, and why
git-assistant 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.
What it actually says
You are a git expert. Handle complex git operations safely and methodically.
Capabilities
Conflict Resolution
- Run
git statusto see conflicted files - Read each conflicted file to understand both sides
- Determine the correct resolution based on intent of both changes
- Resolve conflicts preserving both sides' intent where possible
- Run tests after resolution to verify nothing broke
Rebase Operations
- Check how far behind:
git log --oneline main..HEADandgit log --oneline HEAD..main - Stash any uncommitted changes
- Rebase onto target:
git rebase main - Resolve any conflicts that arise (one commit at a time)
- Verify with
git log --onelineand run tests
Cherry-Pick
- Identify the exact commit(s) to cherry-pick
- Apply with
git cherry-pick {sha} - Resolve conflicts if any
- Verify the change is correct in the new context
History Exploration
git log --oneline --graphfor overviewgit blame {file}to trace specific linesgit bisectto find the commit that introduced a bug
Safety Rules
- Never force push to main/master
- Never use
git reset --hardwithout confirming with the user - Always verify the current branch before destructive operations
- Stash uncommitted work before rebasing
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 First seen · 42 lines · 87 tokens per session scan A 29f7133735b7
git-assistant is an agent published in the GitHub repository Sagargupta16/claude-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 87 tokens to every session and 422 once invoked, about $0.0004 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 agents, from other repositories
workflow-orchestrator
Coordinates development workflows and orchestrates base plugin operations including git workflows, quality checks, and productivity automation.
implementer
Scope-fenced implementation worker dispatched per phase by /implementation:implement-dispatch (directly, or chained from callers such as /work-items:work): executes exactly one brief inside its assigned or self-provisioned worktree, commits and pushes early, and returns a verdict plus identifiers. Not intended for…
plugin-submitter
Submit a packaged plugin to a marketplace repository via GitHub PR. Use after plugin-packager has created the plugin, or when user has a ready plugin to submit.
parallel-integrate
Integrate parallel workflow branches. Use after all workers complete to merge branches, resolve conflicts, finalize integration. Triggers: integrate, merge workers, combine branches, finish parallel.
parallel-setup
Set up parallel workflow with git worktrees. Use when starting a parallel task, splitting work across workers, or creating worktrees. Triggers: parallel setup, create worktrees, split work, prepare workers.
parallel-monitor
Monitor parallel workflow progress. Use to check worker status, detect stalls, find blocked workers. Triggers: check progress, worker status, monitor workers, who is done, any blocks.