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/dryvist/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/dryvist/claude-code-plugins/git-workflows)<a href="https://agentmods.dev/plugins/dryvist/claude-code-plugins/git-workflows"><img src="https://agentmods.dev/badge/plugins/dryvist/claude-code-plugins/git-workflows/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/dryvist/claude-code-plugins/git-workflows"><img src="https://agentmods.dev/badge/plugins/dryvist/claude-code-plugins/git-workflows.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
git-workflows 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 5d 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
{
"name": "git-workflows",
"version": "6.4.0",
"description": "Git main branch synchronization, troubleshooting, and post-merge cleanup workflows",
"author": {
"name": "JacobPEvans"
},
"license": "Apache-2.0",
"repository": "https://github.com/JacobPEvans/claude-code-plugins",
"keywords": [
"git",
"worktree",
"sync",
"branch",
"workflow"
],
"skills": [
"./skills/sync-main",
"./skills/troubleshoot-rebase",
"./skills/troubleshoot-precommit",
"./skills/troubleshoot-worktree",
"./skills/pre-commit-architecture",
"./skills/git-flow-next",
"./skills/git-workflow-standards"
]
}
What it installs
The manifest is a name and a version. 7 skills travel with it, and installing the plugin installs all of them — 299 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 5d ago Changed 1d5db2a560df
- 14d ago Changed 372325002fe5
- 25d ago Changed · +1 lines 99e70c68660d
- 1mo ago Changed a4d2769ed736
- 1mo ago Changed db60ad1b3300
- 1mo ago Changed 3e3f006dd052
- 1mo ago Changed be0ec983b82e
- 1mo ago First seen · 26 lines scan A 8d3fe255d85e
git-workflows is a plugin published in the GitHub repository dryvist/claude-code-plugins (3 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-31.
Other plugins, from other repositories
pr-provenance-stamp
Embeds a reviewer-facing provenance receipt into your PR body when Claude runs gh pr create (or glab mr create). A PostToolUse hook (async, zero added latency) records a per-session ledger: tool calls, agent-authored lines, and every test/typecheck command with its real exit code; a PreToolUse (Bash) hook then rewr.
auto-stage
Automatic git staging for Claude Code. A PostToolUse hook on Edit|Write runs git add on every file Claude modifies, so git status always shows exactly what Claude touched and pre-commit review needs no manual staging. Files outside a git repo are skipped, .gitignore is respected (ignored files fail to stage and the.
hydra
Git Worktree management for parallel agent execution - isolated working directories without Git conflicts.
harness-kit
Claude Code harness for product + engineering delivery. From idea to merged PR, one pipeline. Run /harness-kit:install to set it up in your project.
gate-router
Map changed Git files to local verification commands.
gh-tools
GitHub workflow automation: GFM link validation, WebFetch enforcement, issue management, fork intelligence.