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.
git clone --depth 1 https://github.com/motlin/claude-code-pluginsWrote 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/plugins/motlin/claude-code-plugins/git)<a href="https://agentmods.dev/plugins/motlin/claude-code-plugins/git"><img src="https://agentmods.dev/badge/plugins/motlin/claude-code-plugins/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/plugins/motlin/claude-code-plugins/git"><img src="https://agentmods.dev/badge/plugins/motlin/claude-code-plugins/git.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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 3d 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
{
"$schema": "https://anthropic.com/claude-code/plugin.schema.json",
"name": "git",
"description": "Git workflow automation with smart commits, conflict resolution, rebase management, worktree creation, and worktree cleanup",
"version": "1.37.0",
"license": "Apache-2.0",
"author": {
"name": "Craig Motlin"
},
"skills": ["./skills/git-workflow"]
}
What it installs
The manifest is a name and a version. 12 skills travel with it, and installing the plugin installs all of them — 526 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill wip A 134 tokens
- Skill git-cleanup A 80 tokens
- Skill reword-commits A 45 tokens
- Skill split-branch A 34 tokens
- Skill commit A 20 tokens
- Skill rebase-all A 33 tokens
- Skill worktree A 38 tokens
- Skill git-rebase A 19 tokens
- Skill clean-worktrees A 29 tokens
- Skill git-workflow A 34 tokens
- Skill conflicts A 33 tokens
- Skill commit-chunks A 27 tokens
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.
- 3d ago Changed 00ed412b19ec
- 6d ago Changed c8fdd4002755
- 9d ago Changed a1030472a472
- 22d ago Changed · -1 lines 9704390d09f2
- 29d ago Changed 752aacb9d5d9
- 1mo ago Changed · -10 lines f0c895220c79
- 1mo ago Changed e2265e36cfb3
- 1mo ago Changed cc84573e94dd
- 1mo ago Changed 86105d04c293
- 1mo ago First seen · 23 lines scan A 1e6a17701318
git is a plugin published in the GitHub repository motlin/claude-code-plugins (20 stars, last pushed yesterday), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
git-sidebar
A lazygit-style side pane: every worktree of the repository and its local branches as rows you click. A worktree row moves the session there with /cd; a branch row shows its last commits and offers switch (clean tree only) or open worktree. Docked floor to ceiling beside the transcript in the fullscreen layout, above…
git
Git workflow tools: commits, PRs, review inbox, checkout, and work triage.
git-pr
Committing, PR creation and review triage, and dependency upgrades.
cas
Evidence-driven research, guarded Codex delegation, explicit native parallelism, secret protection, and approval gates for rm, commit, and push.
code-quality
OxLint, Biome, and Prettier configuration, linting skills, and pre-commit hooks for consistent code quality.
prek
Set up git pre-commit hooks with prek, the fast pre-commit-compatible runner.