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/cboone/agent-harness-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/cboone/agent-harness-plugins/use-git)<a href="https://agentmods.dev/plugins/cboone/agent-harness-plugins/use-git"><img src="https://agentmods.dev/badge/plugins/cboone/agent-harness-plugins/use-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/cboone/agent-harness-plugins/use-git"><img src="https://agentmods.dev/badge/plugins/cboone/agent-harness-plugins/use-git.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
use-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 15d 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
{
"author": {
"name": "Christopher Boone"
},
"description": "Apply git and GitHub CLI conventions for tmpfile bodies, signed commits and safe pushes, and create GitHub issues.",
"homepage": "https://github.com/cboone/agent-harness-plugins",
"keywords": ["cli", "conventions", "gh", "git", "github", "permissions"],
"license": "MIT",
"name": "use-git",
"repository": "https://github.com/cboone/agent-harness-plugins",
"skills": "./skills",
"version": "1.3.2"
}
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 94 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.
- 15d ago Changed d6cd19fc278d
- 20d ago Changed 162e47414285
- 1mo ago Changed 24bdb2f8d9d3
- 1mo ago Changed 8dec42d8c42e
- 1mo ago Changed 9582cf4166c8
- 1mo ago Changed ccd81803d005
- 1mo ago Changed 433cd39b06ad
- 1mo ago Changed 0ceb85148f34
- 1mo ago First seen · 14 lines scan A af6e3c218ecb
use-git is a plugin published in the GitHub repository cboone/agent-harness-plugins (2 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-09-03.
Other plugins, from other repositories
aidd-vcs
External artifacts: repo-init, commit, pull-request, release-tag, issue-create, resolve-conflict.
comfyui-plugin
ComfyUI custom-node pack lifecycle - scaffold a pack, create + seed the repo, open the gitops adoption PR, publish to the Comfy Registry, and add README screenshots.
gitflow-cli
Gitflow CLI workflows and repository skills for Claude Code.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.
claude-plugins-official marketplace
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.