configure-pre-commit

configure-pre-commit is a skill for Claude Code from laurigates/claude-plugins. It costs 47 tokens per session (1,930 once invoked), scanned A, original, MIT.

A setup and audit guide for pre-commit hooks, which are automatic checks that run before Git records a commit.

In plain words
What is it for?
Use it to install or migrate to the pre-commit framework, check compliance, select hooks for the project type, and update hook configuration.
Why use it?
It helps catch formatting, linting, or other project-standard problems before they enter the repository.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Part of the configure-plugin plugin — 48 skills shipped together

Good fit Use it to install or migrate to the pre-commit framework, check compliance, select hooks for the project type, and update hook configuration.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/laurigates/claude-plugins/configure-pre-commit
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.

Any agent
npx skills add laurigates/claude-plugins --skill configure-pre-commit
Clone the repo
git clone --depth 1 https://github.com/laurigates/claude-plugins

Made for: Claude Code.

Or install configure-plugin, the plugin that ships this one along with the rest of its 48 skills.

Wrote 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.

agentmods badge for configure-pre-commit

README.md
[![agentmods](https://agentmods.dev/badge/skills/laurigates/claude-plugins/configure-pre-commit/github.svg)](https://agentmods.dev/skills/laurigates/claude-plugins/configure-pre-commit)
Your own site
<a href="https://agentmods.dev/skills/laurigates/claude-plugins/configure-pre-commit"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/configure-pre-commit/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.

agentmods 80×15 button for configure-pre-commit

Your own site · 80×15
<a href="https://agentmods.dev/skills/laurigates/claude-plugins/configure-pre-commit"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/configure-pre-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,930 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00047 $0.01930
Opus 5.5 $0.00019 $0.00772
Sonnet 5.5 $0.00009 $0.00386
Haiku 4.5 $0.00005 $0.00193

Measured 9d ago against content hash 81bee4878843, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

configure-pre-commit 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 9d 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.

configure-plugin/skills/configure-pre-commit/SKILL.md · 172 lines

How it starts

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

/configure:pre-commit

Check and configure pre-commit hooks against project standards.

When to Use This Skill

Use this skill when... Use another approach when...
Setting up or validating pre-commit hooks Project doesn't use pre-commit framework (use git hooks directly)
Checking compliance with project standards Just running hooks manually (use pre-commit run command)
Installing project-type-specific hooks Hooks are already properly configured
Migrating to pre-commit framework Simple project with no quality checks needed
Updating hook configurations for detected tools Need to disable pre-commit entirely

Context

  • Pre-commit config: !find . -maxdepth 1 -name \'.pre-commit-config.yaml\'
  • Project standards: !find . -maxdepth 1 -name \'.project-standards.yaml\'
  • Project type in standards: !find . -maxdepth 1 -name '.project-standards.yaml' -exec grep -m1 "^project_type:" {} +
  • Has terraform: !find . -maxdepth 2 \( -name '*.tf' -o -type d -name 'terraform' \) -print -quit
  • Has helm: !find . -maxdepth 2 -type d -name 'helm' -print -quit
  • Has package.json: !find . -maxdepth 1 -name \'package.json\'
  • Has pyproject.toml: !find . -maxdepth 1 -name \'pyproject.toml\'

Parameters

Parse from $ARGUMENTS:

  • --check-only: Report status without offering fixes
  • --fix: Apply all fixes automatically without prompting
  • --type <type>: Override project type detection (frontend, infrastructure, python)

Execution

Execute this pre-commit compliance check:

Step 1: Detect project type

  1. Read .project-standards.yaml for project_type field if it exists
  2. If not found, auto-detect:
    • infrastructure: Has terraform/, helm/, argocd/, or *.tf files
    • frontend: Has package.json with vue/react dependencies
    • python: Has pyproject.toml or requirements.txt
  3. Apply --type flag override if provided

Step 2: Check configuration file

Read the full file on GitHub · 172 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

  1. 9d ago Changed · +5 lines 81bee4878843
  2. 25d ago Changed · +14 tokens per session ece2b9e9d4e3
  3. 1mo ago First seen · 167 lines · 33 tokens per session scan A 4360792622be

Subscribe to this mod's changes

configure-pre-commit is a skill published in the GitHub repository laurigates/claude-plugins (60 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 1,930 once invoked, about $0.0002 per session on Opus 5.5. 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.

Related

Other skills, from other repositories

openclaw-parallels-smoke

End-to-end Parallels smoke, upgrade, and rerun workflow for OpenClaw across macOS, Windows, and Linux guests. Use when Codex needs to run, rerun, debug, or interpret VM-based install, onboarding, gateway smoke tests, latest-release-to-main upgrade checks, fresh snapshot retests, or optional Discord roundtrip…

SafeAI-Lab-X/ClawKeeper · 85 tokens

model-merging

Merge multiple fine-tuned models using mergekit to combine capabilities without retraining. Use when creating specialized models by blending domain-specific expertise (math + coding + chat), improving performance beyond single models, or experimenting rapidly with model variants. Covers SLERP, TIES-Merging, DARE, Task…

davila7/claude-code-templates · 73 tokens

mem0-test-integration

Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…

mem0ai/mem0 · 207 tokens

cw-gates

Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.

Hmbown/Codewhale · 48 tokens

workflow-patterns

Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.

wshobson/agents · 35 tokens

release-safety

Release safety rules. INVOKE WHEN: yarn release, npm publish, release canary, release packages, publishing, skip checks, skip tests. NEVER skip checks or tests without explicit permission.

tamagui/tamagui · 0 tokens