What is setup-git-hooks?

A command that installs Git hooks, which are scripts Git runs at events such as commits and pushes.

Use it to detect the project type and existing checks, configure them interactively, and install pre-commit, pre-push, or commit-message checks.

It catches formatting, lint, test, and commit-message problems before changes are committed or pushed.

setup-git-hooks — Command by bacchus-labs

Install

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.

agentmods

npx agentmods add commands/bacchus-labs/wrangler/setup-git-hooks

Clone the repo

git clone --depth 1 https://github.com/bacchus-labs/wrangler

Or install wrangler, the plugin that ships this one along with the rest of its 25 skills, 16 commands, 16 agents.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 750 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00750
Opus 5	$0.00000	$0.00375
Sonnet 5	$0.00000	$0.00150
Haiku 4.5	$0.00000	$0.00075

Measured 2d ago against content hash 8c58df5ae3d8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

setup-git-hooks 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 2d 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.

commands/setup-git-hooks.md · 122 lines

How it starts

The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/wrangler:setting-up-git-hooks

Set up Git hooks for automated testing and code quality enforcement.

Description

This command helps you configure and install Git hooks in your project to enforce testing and code quality standards before commits and pushes. It provides an interactive setup experience with smart project detection.

What It Does

Detects your project type (JavaScript, Python, Go, etc.)
Finds existing test/lint/format commands from project files
Asks configuration questions with sensible defaults
Generates hook configuration (.wrangler/config/hooks-config.json)
Installs hooks to .git/hooks/ or .wrangler/config/git-hooks/
Creates documentation templates (TESTING.md, security checklist, etc.)

Usage

Simply run the command:

/wrangler:setting-up-git-hooks

Follow the interactive prompts to configure your hooks.

Hooks Installed

Hook	When	What It Does
`pre-commit`	Before each commit	Runs formatter, linter, unit tests
`pre-push`	Before push to protected branches	Runs full test suite
`commit-msg`	On commit (optional)	Validates commit message format

Installation Patterns

Pattern A: Direct Installation (Default)

Hooks installed directly to .git/hooks/. Configuration in .wrangler/config/hooks-config.json.

Best for: Individual developers, small teams

Pattern B: Version-Controlled

Hooks stored in .wrangler/config/git-hooks/ and symlinked via install script.

Best for: Teams that want hooks in version control, consistent setup across team

Bypass Mechanism

For TDD RED phase or emergency fixes:

WRANGLER_SKIP_HOOKS=1 git commit -m "WIP: failing test for feature X"

Note: This bypass is only available to humans. AI agents cannot set environment variables, ensuring they always follow the enforcement rules.

Examples

Basic Setup

/wrangler:setting-up-git-hooks

After Setup

Read the full file on GitHub · 122 lines

Changes

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.

2d ago First seen · 122 lines · 0 tokens per session scan A 8c58df5ae3d8

Subscribe to this mod's changes

setup-git-hooks is a command published in the GitHub repository bacchus-labs/wrangler (4 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 750 tokens. 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.

setup-git-hooks