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/karanb192/claude-code-hooksWrote 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/karanb192/claude-code-hooks/auto-stage)<a href="https://agentmods.dev/plugins/karanb192/claude-code-hooks/auto-stage"><img src="https://agentmods.dev/badge/plugins/karanb192/claude-code-hooks/auto-stage/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/karanb192/claude-code-hooks/auto-stage"><img src="https://agentmods.dev/badge/plugins/karanb192/claude-code-hooks/auto-stage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
auto-stage 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": "auto-stage",
"description": "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 failure is logged, never forced), and the git call is shell-free so hostile filenames cannot inject commands.",
"version": "1.0.0",
"author": {
"name": "Karan Bansal",
"url": "https://github.com/karanb192"
},
"homepage": "https://github.com/karanb192/claude-code-hooks",
"license": "MIT",
"keywords": [
"claude-code",
"hooks",
"git",
"staging",
"automation",
"posttooluse"
]
}
What it installs
The manifest is a name and a version. 1 hook travel with it, and installing the plugin installs all of 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 · 20 lines scan A cc031f6de6b3
auto-stage is a plugin published in the GitHub repository karanb192/claude-code-hooks (542 stars, last pushed 13d 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
hydra
Git Worktree management for parallel agent execution - isolated working directories without Git conflicts.
diffctx
Selects the minimum code an LLM needs to review a git diff.
git-workflows
Git main branch synchronization, troubleshooting, and post-merge cleanup workflows.
branch-guard
Cut routine git/gh approval prompts: auto-approve safe commands (read-only, staging, branch/worktree create, feature-branch commits & pushes) and confirm protected-branch or destructive ones.
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.
branch-recap
Tells you what your branch actually changed — what was done, why, and what deserves a second look, instead of the diff — then files the fixes into the commits they belong to.