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/FradSer/dotclaudeWrote 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/fradser/dotclaude/git)<a href="https://agentmods.dev/plugins/fradser/dotclaude/git"><img src="https://agentmods.dev/badge/plugins/fradser/dotclaude/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/fradser/dotclaude/git"><img src="https://agentmods.dev/badge/plugins/fradser/dotclaude/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 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.
What it actually says
{
"name": "git",
"version": "0.6.2",
"description": "GitFlow workflow automation for feature, hotfix, and release branches with post-finish cleanup",
"displayName": "Git",
"author": {
"name": "Frad LEE",
"email": "[email protected]"
},
"license": "MIT",
"keywords": [
"git",
"workflow",
"version-control",
"gitflow"
],
"commands": [
"./skills/start-feature/",
"./skills/finish-feature/",
"./skills/start-hotfix/",
"./skills/finish-hotfix/",
"./skills/start-release/",
"./skills/finish-release/",
"./skills/commit/",
"./skills/commit-and-push/"
]
}
What it installs
The manifest is a name and a version. 6 skills travel with it, and installing the plugin installs all of them — 409 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.
- 1mo ago First seen · 28 lines scan A dd1ab465bbd0
git is a plugin published in the GitHub repository FradSer/dotclaude (593 stars, last pushed 7d ago), 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-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.
digest
Summarize AI-generated branches, PRs, and diffs into icon-rich cards, explain code state with git archaeology as self-contained HTML explainers, plus multi-project weekly recall digests.
code-quality
OxLint, Biome, and Prettier configuration, linting skills, and pre-commit hooks for consistent code quality.
feature-to-pr-factory
Turn one feature into dependency-ordered GitHub or GitLab issues, then build each ticket into its own reviewed, tested PR or MR with agents.