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 skills add bntvllnt/agent-skills --skill gitgit clone --depth 1 https://github.com/bntvllnt/agent-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/skills/bntvllnt/agent-skills/git)<a href="https://agentmods.dev/skills/bntvllnt/agent-skills/git"><img src="https://agentmods.dev/badge/skills/bntvllnt/agent-skills/git/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/bntvllnt/agent-skills/git"><img src="https://agentmods.dev/badge/skills/bntvllnt/agent-skills/git.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.00066 | $0.00808 |
| Opus 5.5 | $0.00026 | $0.00323 |
| Sonnet 5.5 | $0.00013 | $0.00162 |
| Haiku 4.5 | $0.00007 | $0.00081 |
Grade A, and why
git 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git
Clear, repeatable git workflow with a bias toward safety.
Router
Use the smallest workflow that matches the user intent.
| User says | Load reference | Do |
|---|---|---|
| status / what changed (no "worktree" prefix) | references/read-only.md |
read-only inspection |
| help / usage / man | references/cli-help.md |
show CLI help safely |
| commit / stage | references/commit-workflow.md |
stage + commit safely |
| branch / switch | references/branch-workflow.md |
branch operations |
| worktree create/remove/list | references/worktree-workflow.md |
worktree operations |
| worktree cleanup / normalize / consolidate | references/worktree-maintenance.md |
auto-clean + consolidate worktrees |
| worktree summary / worktree status / show worktrees | references/worktree-summary.md |
proactive analysis: PR status, change classification, safe-to-delete verdicts |
| tag / version | references/tag-workflow.md |
create/list/inspect tags |
| pr / pull request | references/pr-workflow.md |
create/update PR via gh |
| pr review / fix pr comments / threads | references/pr-review-workflow.md |
review + respond + fix |
| merge / rebase / reset / revert | references/advanced-workflows.md |
advanced/recovery (confirm first) |
Config (Edit Here)
Worktree working directories (the folders you cd into) live outside .git/.
Set this once and use it everywhere:
WORKTREES_DIR=./.worktrees
WORKTREE_PATH=$WORKTREES_DIR/<topic>
If you want a different location (e.g. ../.worktrees or ~/worktrees/<repo>), update WORKTREES_DIR above and follow the same shape in references/worktree-workflow.md.
Resilience Rules (Worktrees)
- If multiple worktree root folders are detected (example: both
./.worktrees/and../repo-feature-x/exist), do not delete anything by default. - Prefer consolidating into
WORKTREES_DIRusinggit worktree move(when possible) or a remove+re-add plan. - If stale metadata exists, propose a cleanup plan:
git worktree prune+ remove/quarantine orphan directories (with confirmation).
What ships with it
12 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.
- README.md 1.1 KB
- references/advanced-workflows.md 580 B
- references/branch-workflow.md 514 B
- references/cli-help.md 364 B
- references/commit-workflow.md 1.4 KB
- references/pr-review-workflow.md 422 B
- references/pr-workflow.md 452 B
- references/read-only.md 400 B
- references/tag-workflow.md 1.1 KB
- references/worktree-maintenance.md 1.5 KB
- references/worktree-summary.md 7.6 KB
- references/worktree-workflow.md 3.2 KB
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 · 86 lines · 66 tokens per session scan A 15bc227d9f56
git is a skill published in the GitHub repository bntvllnt/agent-skills (17 stars, last pushed 4mo ago), licensed MIT. It adds 66 tokens to every session and 808 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-30.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
comet-safe-delivery
A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.
git-master
Advanced Git operations — rebase, squash, fixup, blame, bisect, reflog, code archaeology (git log -S/-G), worktrees. Use when the task mentions rebase, squash, bisect, blame, reflog, fixup, finding deleted code, tracing commit history, cleaning up a branch, or recovering lost work.
release
Verify, write the CHANGELOG, cut a version — then hand the release sequence back.
changelog
Use when writing a changelog or release notes. Covers what belongs in one, writing for users rather than for git, semantic versioning, and documenting breaking changes so nobody is surprised. Trigger on "write release notes for v2.3", "update the changelog", "is this a major or minor version bump". Do not use for…
git-workflow
Use for branching, committing, history repair, and release hygiene. Covers atomic commits, rebase versus merge, bisect, reflog recovery, and undoing mistakes safely. Trigger on "undo my last commit", "i messed up a rebase", "squash these commits", "find which commit broke this". Do not use for pipeline and deploy…