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/joaquimscosta/arkhe-claude-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/joaquimscosta/arkhe-claude-plugins/git)<a href="https://agentmods.dev/plugins/joaquimscosta/arkhe-claude-plugins/git"><img src="https://agentmods.dev/badge/plugins/joaquimscosta/arkhe-claude-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/joaquimscosta/arkhe-claude-plugins/git"><img src="https://agentmods.dev/badge/plugins/joaquimscosta/arkhe-claude-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 today.
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
{
"name": "git",
"description": "Git workflow automation (commit, PR, branching, changelog)",
"version": "1.2.0",
"contextFileName": "GEMINI.md"
}
What ships with it
13 files beside gemini-extension.json 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.
- commands/changelog.toml 1.3 KB
- commands/cleanup-branches.toml 1.4 KB
- commands/commit.toml 1.4 KB
- commands/create-branch.toml 973 B
- commands/create-pr.toml 1.5 KB
- commands/release-please-setup.toml 1.4 KB
- commands/release.toml 1.2 KB
- commands/resolve-review.toml 994 B
- commands/stale-branches.toml 1.2 KB
- commands/worktree.toml 1.0 KB
- GEMINI.md 5.4 KB
- plugin.json 121 B
- skills 24 B
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.
- today First seen · 7 lines scan A 173def619f92
git is a plugin published in the GitHub repository joaquimscosta/arkhe-claude-plugins (21 stars, last pushed today), licensed MIT. 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-10-16.
Other plugins, from other repositories
contributor-writing
Writing skills for Shopware core contributors: Architecture Decision Records, PR descriptions (trunk and feature-branch formats), commit messages, and RELEASEINFO/UPGRADE entries. Analyzes branch diffs, classifies changes, and writes content calibrated to change magnitude.
github-workflow
Git commit, PR creation, review, and merge skills following Conventional Commits.
git
Version-control skills for the whole branch lifecycle: committing, worktrees, merge conflicts, undo/recovery, PR descriptions, changelogs, releases, and branch cleanup.
create-pr
Streamlines pull request creation by handling the entire workflow: creating a new branch, committing changes, formatting modified files with Biome, and submitting the PR.
ship
Complete PR workflow from commit to production with validation.
changelog-generator
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes.